Just can't stay away
Joined: 2006/12/1 18:01 Last Login
: Yesterday 23:02
From Copenhagen, Denmark
Group:
Registered Users
|
@TSK
It might actually not really be corrupted at all. IIRC, this file is always written as exactly the length of a block (or a multiple thereof) which can be updated directly in situ, so that it will not risk corrupting an FFS filesystem if a reset is made during the writing of a history entry. So it will typically contain something resembling a reasonable history list, followed by random data to fill up the block.
Could that be what you're seeing?
If so, it is also not surprising that if you force the file to have another length by "repairing" it, it is no longer valid to ASyncWB.
Best regards,
Niels
|