Yes, I've seen it personally and it has been reported here as well by several others, I do believe. All it takes is the loss of the hidden .Type30 file inside the directory to cause this issue as the hashed file is no longer a dynamic one. It can then fall back on this funky (type 1? 19?) "hashed file" where every record is written out as a separate file.
As you noted, the correct solution is to nuke it and let it rebuild from scratch.
Edit: found another post on the subject.
Corrupted hashed files after server crash
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 14
- Joined: Mon Jan 19, 2009 9:06 pm
When you create the hashed file/s you are better off deleting and recreating them (if possible) for this (amongst other) reason.
IHTH... (I hope This Helps)
IHTH... (I hope This Helps)
Roy R.
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Whereas in my experience, deleting and recreating them each time has been at the root of this issue. I tended to stick with "Clear" unless I had a good reason to nuke them each time and that would generally involve dynamic setting of the Minimum Modulus based on wildly variable volumes. Different strokes.roy wrote:When you create the hashed file/s you are better off deleting and recreating them (if possible) for this (amongst other) reason.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Craig,
I beg to differ!
In my humble opinion (from experience) any hashed file that is used for a long period using the clear option never being deleted and created a new, is bound to eventually get corrupted.
I beg to differ!
In my humble opinion (from experience) any hashed file that is used for a long period using the clear option never being deleted and created a new, is bound to eventually get corrupted.
Roy R.
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
And in my experience I've found them to be quite resilient and really only saw "corruption" for issues like (lack of) disk space, going over the dreaded 2GB barrier with 32bit addressing or by writing funky data to them. Otherwise, solid. Like I said, different strokes.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers