Progress!

[swestrup]

It seems like I DID have filesystem corruption after all. I thought that when 'fsck.reiserfs /mnt/system' returned immediately it meant that everything was fine. Nope. It means that fsck.reiserfs doesn't work on mounted filesystems. When I gave the same command on /dev/md5, it found all sorts of problems and I was forced to rebuild the file tree.

That has now finished and fsck.reiserfs claims it didn't find anything it couldn't fix, and that the filesystem is now clean. Yay!

I'm starting to get pretty damn tired now, so I'll leave it there. Besides, right now I don't think there'll be any trouble finishing the job in the morning, so my stress levels are low, and I should be able to sleep.

Were I to continue, and something ELSE were to crop up, I would not be willing to leave it alone and just go to bed, and who knows what damage I could inflict while too tired to work well, but too anxious to sleep...

So, at this point, sleep is the better part of valour.

Comments

[pphaneuf.livejournal.com]

I'd recommend you do a "dd if=/dev/md0 of=/dev/null" and monitor for errors in the kernel messages (dd might complain on it's stderr as well). Like cpirate says, disk errors are a very common cause for reiserfs corruption, and just reading the whole disk could expose badness.

See you later tonight for your birthday party!