there was work but you don't have enough disk space allocated

hy what does this mean ?

i take the standard pref for home..
i have about 50GB free disk space


now i change the pref to 5GB but it wont work ;-(

Serriously if any one knows the aloution to this problem I would like to know also.
I had hoped that 20 gigs would be enough, but alas.

That was supposed to be solution not alution. sorry new fingers.

I've tried many different settings day after day on disk space to get at least ONE wu downloaded, but I seem to never to have enough disk space... on my AlBook G4 of all things (or so the "command-line" tells me so - oh whoopty-do)!!! It seems like while everyone else is happily chomping away on wu's (on Windows clients, maybe ^_~ ???), something totally different just isn't working here in the Mac world. Man, don't go GM with Boink until you can get all the bugs worked out! Oh well, I'll just stick to the good ol' tried-and-true "classic" 1 wu/download SETI client until then and try to hit that big 500 mark ^_^ ...
*sorry, end ramblings now*

Peace,
Eric

Hello,

Try this thread... it may help, but then again, it may not :p heheh:

http://setiweb.ssl.berkeley.edu/forum_thread.php?id=602

Still waiting for those wu though. Good luck!

Peace,
Eric

I have an 15" Aluminum PowerBook, 74.52GB drive, 26.1GB available space on the drive. I'm running OS X 10.3.4.

My seti disk limits are set to "use no more than" 4GB, "Leave at least" 1GB, "Use no more than" 5% of total space, which on a 74.52GB drive would be 3.726GB which is just under the 4GB "Use no more than" limit. So I should be able to handle just about any work unit set. I've asked for enough work on disk to last between .1 and .3 days, a minimal amount. I've tried setting this to .1 to 1.0 days but that gets the same results, no work units due to not having enough disk space.

I consistently get the message: ...there was work but you don't have enough disk space allocated...

I've experimented for almost a week now trying each end of the settings, waiting my hour each time for Boinc to do its thing, and get the same message back.

Anyone been successful? What is the trick? My guess is that it is a bug in the SETI client/server communication and possibly unique to the OS X Unix environment, I'm now running Boinc 3.19 and getting the same messages as 3.18. Here is the terminal file:




Last login: Tue Jul 13 17:12:03 on ttyp1
Welcome to Darwin!
pldmac:~ pderby$ cd /
pldmac:/ pderby$ cd Applications
pldmac:/Applications pderby$ ./boinc_3.19_powerpc-apple-darwin
2004-07-13 19:46:58 [---] Starting BOINC client version 3.19 for powerpc-apple-darwin
2004-07-13 19:46:58 [SETI@home] Project prefs: using your defaults
2004-07-13 19:46:58 [SETI@home] Host ID is 65583
2004-07-13 19:46:58 [---] General prefs: from SETI@home (last modified 2004-07-12 12:09:57)
2004-07-13 19:46:58 [---] General prefs: using your defaults
2004-07-13 19:46:58 [---] Fewer active results than CPUs; requesting more work
2004-07-13 19:46:58 [SETI@home] Requesting 23050 seconds of work
2004-07-13 19:48:23 [SETI@home] Sending request to scheduler: http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi
2004-07-13 19:49:10 [SETI@home] Scheduler RPC to http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi succeeded
2004-07-13 19:49:10 [SETI@home] Message from server: No work available (there was work but you don't have enough disk space allocated)
2004-07-13 19:49:10 [SETI@home] Message from server: No work available (there was work but you don't have enough disk space allocated)
2004-07-13 19:49:10 [---] General prefs: from SETI@home (last modified 2004-07-12 12:09:57)
2004-07-13 19:49:10 [---] General prefs: using separate prefs for home
2004-07-13 19:49:10 [SETI@home] Project prefs: no separate prefs for home; using your defaults
2004-07-13 19:49:10 [SETI@home] No work from project
2004-07-13 19:49:10 [SETI@home] No work from project
2004-07-13 19:49:10 [SETI@home] Deferring communication with project for 1 hours, 0 minutes, and 0 seconds
2004-07-13 19:49:10 [SETI@home] Deferring communication with project for 1 hours, 0 minutes, and 0 seconds