GetVolumeInformation failed
28 Mar 2005 8:10:59 UTC
Topic 188773
(moderation:
Hi, I'm using boinc for windows running under wine. First all worked fine, but recently i'm getting this message:
zip diagnostic: GetVolumeInformation failed
zip diagnostic: GetVolumeInformation failed
adding: H1_0354.4__0354.9_0.1_T15_Test02_1_0 (deflated 65%)
and after that computation stops.
I have to restart boinc(wine) to continue. The odd thing is, that after restarting wine, boinc claims, that unit is done and is starting new one.
The unit is actually done(it's granted credits), but boinc claims strangly small amount of credits, or even zero (expample).
Did whoever notice this behavior or knows what the message means ?
GetVolumeInformation failed
)
The claimed credit is based on benchmarks that may give complete nonsense on emulators such as Wine. You will get the median credit of a Quorum for your results, so no need to worry too much about it.
After successful computation the output file is compressed before uploading to reduce the upload size. If the compression fails (like in your case) the file is uploaded uncompressed. The Validator will correctly handle both types of uploaded files. So both issues shouldn't pose serious problems for you.
I have, however, no idea why the compression fails on (your) Wine. Which version of Wine are you using?
BM
BM
wine-20050211-1rh73winehq,
)
wine-20050211-1rh73winehq, boinc 4.24
If the error message is only about compression, I will not care about it.
The claimed credits are so low not because of benchmark.
If, the computation doesn't stop - it claims normal amount of credits.
But as You advised, I don;t care about credits.
But I do care about computation stop. It stops, and runs nothing until I restart wine by hand.
I suspect/sure that problem is related to wine or Xserver...
I see. Well, I have no
)
I see. Well, I have no experience running the Windows Client on Wine yet, maybe someone else can help with that...
BM
BM
I discovered, that 1. zip
)
I discovered, that
1. zip error has nothing to do with computation stop.
2. the computation stop occurs becouse boinc loses connection to core.
I think it's true because yesterday i noticed, that client_state.xml wasn't updated while core was still running. fraction_done stopped at 0.53.. When I killed boinc(and core) and then started again, the fraction_done jumped to 0.68..
And one more think, just before boinc losed connection to core the stdoutdae.txt said:
[---] Running CPU benchmarks
[---] Suspending computation and network activity - running CPU benchmarks
- after that no updates to fraction_done.
This would also explain why claimed credits are strangely low (or zero).
Boinc thiks that core did it's work in say 0.53... of total time.
Of course this not explains why this happens, but maybe it's a trace for somebody.
And to remaind: boinc 4.24 run under wine.