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

[sps.livejournal.com]

...And I was worried when you said that you had started by mounting everything. Really, when the fs is corrupt, you do NOT want to mount it!

[pphaneuf.livejournal.com]

The trick part is also that with reiser, you might not necessarily want to run reiserfsck either.

[swestrup]

Yeah, but I had been getting bizarre errors from the raidtools and I wanted to check that the raid partitions that I had finally rebuilt were indeed the ones I was trying to build. I didn't want to run fsck on something that was built out of the wrong set of partitions...

[sps.livejournal.com]

Well, maybe Pierre knows differently, but I would always have said that a read-only fsck was the best way of finding out whether I had found an intact filesystem. A mount is supposed to *do* stuff, and it relies on fsck to have put things in order, first.