Google Drive storage quota has been exceeded
 

Any experience/good answers?

I deleted almost every workfile I no longer need but still get this error.

Is there a TrashBin somewhere I need to clean?

Thanks

[QUOTE=petrw1;559389]I deleted almost every workfile I no longer need but still get this error.

Is there a TrashBin somewhere I need to clean?
[/QUOTE]Yes there is. If you have lots of subfolders you may need to scroll the left pane down to find it.

[QUOTE=kriesel;559397]Yes there is. If you have lots of subfolders you may need to scroll the left pane down to find it.[/QUOTE]

This is all I see:

Seems My Drive is not the same My Drive that colab is using as it has many many more folders

[QUOTE=petrw1;559399]This is all I see:

Seems My Drive is not the same My Drive that colab is using as it has many many more folders[/QUOTE]
trashcan icon left of "BIN". But 6.6MB/15GB is less than 0.1% usage, should not issue a quota complaint.

[QUOTE=kriesel;559401]trashcan icon left of "BIN". But 6.6MB/15GB is less than 0.1% usage, should not issue a quota complaint.[/QUOTE]

Exactly.

Any idea why in my Google Drive I see the Colab Notebooks but I DO NOT see any of the files the notebooks created? Since I can't see them there I deleted files directly from the Colab session (find '...' | exec rm ... ) to try to save space but that made no difference.

[QUOTE=petrw1;559443]Exactly.

Any idea why in my Google Drive I see the Colab Notebooks but I DO NOT see any of the files the notebooks created? Since I can't see them there I deleted files directly from the Colab session (find '...' | exec rm ... ) to try to save space but that made no difference.[/QUOTE]Permissions? Working directory not on Google Drive? Maybe some echo statements, ls-l etc would shed light on what's happening.

[QUOTE=petrw1;559443]Exactly.

Any idea why in my Google Drive I see the Colab Notebooks but I DO NOT see any of the files the notebooks created? Since I can't see them there I deleted files directly from the Colab session (find '...' | exec rm ... ) to try to save space but that made no difference.[/QUOTE]

:richd::groan::censored::bangheadonwall:

I seem to have 2 Google Drives and I was looking at the wrong one.
Sorry all and thanks all

I've been successful with running the free version of the google colab, so I decided to give the google colab pro a go. I keep getting this error below.

[QUOTE]20201019_210109 ( 0:05): DEEP: Can't open workfile worktodo.txt
20201019_210109 ( 0:05): DEEP: ERROR: get_next_assignment(): can't open "worktodo.txt"[/QUOTE]

I tried just putting in the access code, even tried pasting the python code, but still can't get around this error.

Is this a bug from colab pro or something I'm missing?
__________________

Disregard my last post. I figured it out.

Wow got my first Tesla V100 runtime with a [B]free colab [/B]account today.
[CODE]2020-10-19 23:29:23 Tesla V100-SXM2-16GB-0 OpenCL compilation in 2.07 s
2020-10-19 23:29:24 Tesla V100-SXM2-16GB-0 107891659 OK 90400000 loaded: blockSize 400, 12e6dccc55f744f3
2020-10-19 23:29:24 Tesla V100-SXM2-16GB-0 validating proof residues for power 8
2020-10-19 23:32:49 Tesla V100-SXM2-16GB-0 Proof using power 8
2020-10-19 23:32:50 Tesla V100-SXM2-16GB-0 107891659 OK 90400800 83.79%; 657 us/it; ETA 0d 03:12; 986a42ef2d53f9bf (check 0.43s)
2020-10-19 23:34:59 Tesla V100-SXM2-16GB-0 107891659 OK 90600000 83.97%; 646 us/it; ETA 0d 03:06; 19a1a80ecbcf5f78 (check 0.44s)
2020-10-19 23:37:09 Tesla V100-SXM2-16GB-0 107891659 OK 90800000 84.16%; 647 us/it; ETA 0d 03:04; 462a669946f55cf9 (check 0.44s)
2020-10-19 23:39:19 Tesla V100-SXM2-16GB-0 107891659 OK 91000000 84.34%; 646 us/it; ETA 0d 03:02; b6e037727b73b8b7 (check 0.43s)[/CODE]

[QUOTE=moebius;560373]Wow got my first Tesla V100 runtime with a [B]free colab [/B]account today.
[/QUOTE]


Got one several days ago on a free account too. It was insane.

Lucky
 

Every day for the last few week I try to get P-100s for 2 Colab P-1 sessions.
I can't speak for V-100 P-1 times as I've never seen one yet.
But I have to try over and over until I get a P-100 for each session as they are 5-10 times faster than anything else I've been given so far including T4. P4 and K80.
On average I have been requiring 5-20 retries per night. Percentage-wise I estimate:
T4: 95%
P4: 1%
K80: 1%
P100: 3%
V100: 0% so far out of a few hundred tries.