How to deal with corrupt filesystem?

pinga123 · 02-22-2011, 11:29 PM

Hi one of the partition seems to be corrupted .

blade-4 kernel: journal_bmap: journal block not found at offset 3084 on sdc1
blade-4 kernel: Aborting journal on device sdc1.
blade-4 kernel: ext3_abort called.

due to which it is getting remounted in read only mode

After doing some R&D it seems to be issue with journal .
http://www.linuxquestions.org/questi...d-only-362259/
following solution were given to deal with it.

remove the journal:

Code:

tune2fs -O^has_journal /dev/hdxx
Add it back:
tune2fs -j /dev/hdxx

Now i m not sure if it will do any damage to the existing data .

Please suggest.

JZL240I-U · 02-23-2011, 08:20 AM

As far as I can deduce nothing untoward will happen as a result from the three(!) commands (you omitted the file system check)

Code:

tune2fs -O^has_journal /dev/hdxx
e2fsck /dev/hdxx
tune2fs -j /dev/hdxx

Reason: the journal is syncing its data every 5 seconds in the default setting (or did you change that?). So your data were either written out of that journal or there is a small chance that they are corrupt in that journal. In the latter case you don't know which state your files are in anyhow. If you know what you did last, you might take a look at files open during the change in your file system from rw to ro and try to find out the state they are in.

Much less trouble would be: back up or clone the partition and unleash

those commands. If all is well -- okay, else you have that backup and you'll have to restore from there.