Skip to contentSkip to conversation

tail corruptions: saga continues

DISCUSSION Samium Gromoff 1 participant 1 message Sep 14, 2001 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

" Vladimir V. Saveliev wrote:"

Quoted 9 lines

Hi

Quoted 6 lines

Subject: tail corruptions: saga continues
Date: Thu, 13 Sep 2001 00:33:23 +0000 (UTC)
From: Samium Gromoff <[email protected]>
To: [email protected]
CC: [email protected]

Quoted 3 lines
Quoted 1 line
         2.4.7/3.x.0k-pre8 pair in _very_rare_ circumsistances

You should get 3.x.0k-pre9.

Ouch! Actually that was pre9... sorry for a mistake.

Quoted 12 lines
Quoted 11 lines

gives tails corruptions with --rebuild-tree.

Actually i found only one file filled with "." (ofcourse <4k)
As a detail, on sudden reboots i have log tails filled with "."
but it seems to be unrelated.
It may look like this one file "." fill was caused by sudden
inability to sync while corruption raised, but in fact at the moment when fs was corrupted i havent accessed this file for ages... (.c file)

Quoted 2 lines

So, am I correct that before running reiserfsck --rebuild-tree the file contained proper data and did not after it?

Yep

Quoted 5 lines

Or the file appeared corrupted after sudden reboot/mount and it was not touched before that sudden crash?

Why did you decide to run --rebuild-tree? Did reiserfsck --check recommend you to do that?

To repair fs with some blocks set to zero. Zeroified blks are unrelated though...

Quoted 6 lines

Thanks,
vs