 |
KWSN Orbiting Fortress
KWSN Distributed Computing Teams forum
|
| View previous topic :: View next topic |
| Author |
Message |
Atomic Booty
Prince
Joined: 10 Sep 2005
Posts: 589
Location: New Orleans
|
 Posted: Sun Sep 17, 2006 3:16 am Post subject: Lost My Cache! |
 |
|
Not as bad as losing cash I suppose, bit pretty upsetting nonetheless. My computer crashed for stupid Windoze BS, and when I finally got it to reboot properly, all my WUs were gone. I didn't have to reattach to my projects, but BOINC treated my PC like a new host on all of them. I am bummed, had a lot of work in progress.  Does anyone have any idea how this could have happened? I have crashed before and had to revert to an earlier checkpoint, but it's never dumped all its WUs. |
|
| Back to top |
|
 |
Pooh Bear 27
Prince
Joined: 28 Jan 2005
Posts: 1354
Location: Fond du Lac, WI
|
| Posted: Sun Sep 17, 2006 8:11 am Post subject: |
|
|
If it was in the middle of writing any number of files in the BOINC folder, and the write didn't finish when the crash happened, you got the result of what happens.
There are a couple of key files that if corrupt will cause this. One I know is client_state.xml, I believe there might be a couple of others.
Most of us has had this happen. There's not a lot we can do about it.
_________________
Watch the movie about me The 4-1-4s: The Original Teenage Hackers (It is only about 12 minutes long.)
My lucky numbers are 121*2^4553899-1 and 3756801695685*2^666669±1
 |
|
| Back to top |
|
|
Atomic Booty
Prince
Joined: 10 Sep 2005
Posts: 589
Location: New Orleans
|
| Posted: Mon Sep 18, 2006 9:20 pm Post subject: |
|
|
Thanks for the reply, Pooh. I posted this on the Riesel-Sieve boards as well, and their dev had this to say:
| bryan wrote: | Atomic -
I saw the reply over at KWSN - I'm not sure there's really anything that can be done for this queue.
I think, however, that BOINC backs-up the client_state.xml file when it makes the new one. If such a crash happened again, try copying the file client_state_prev.xml to another folder, start BOINC, and see if the client works. If it's corrupted, stop BOINC, copy that client_state_prev.xml to client_state.xml, and start BOINC. It should resume from where it was before it crashed, but I can't guarantee that. Just speculation on my part.
|
Although this was the first time I've experienced this problem, it probably won't be the last, unless of course, it is fixed in a future BOINC version. But if one of you lucky shrubbers beats me to it, and you feel like trying out Bryan's idea, let me know if it works! |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
