Progress!

Nov. 18th, 2005 03:59 am
swestrup: (Default)
[personal profile] 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.

Date: 2005-11-18 03:45 pm (UTC)
From: [identity profile] labyrinthman.livejournal.com
Happy birthday, btw. (if LJ's birthday feature is reporting correctly, that is)

Date: 2005-11-18 03:57 pm (UTC)
From: [identity profile] cpirate.livejournal.com
Happy birthday!

You may want to double-check that the drive is still in good shape; one common source of ReiserFS corruption at work is bad drives. Of course, another large source was power outages (despite ReiserFS being journalled!) - we had to put in a big fat hack to force single-threading for Reiser to put an end to that.

Date: 2005-11-18 05:45 pm (UTC)
From: [identity profile] pphaneuf.livejournal.com
Nah, we didn't leave the "big reiser lock" after all, we disabled tail packing (with the "notail" mount option), which removed most corruption problems on poweroff. There was a bug in the journalling code that dealt with tail packing.

Date: 2005-11-18 05:51 pm (UTC)
From: (Anonymous)
Oh right, my bad. That'll teach me for posting before properly waking up.

Date: 2005-11-18 05:52 pm (UTC)
From: [identity profile] cpirate.livejournal.com
It's 1 in the afternoon, and I'm still not sure I've woken up. That was me. *sigh*

Date: 2005-11-18 05:48 pm (UTC)
From: [identity profile] 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 [livejournal.com profile] 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!

Date: 2005-11-18 06:28 pm (UTC)
From: [identity profile] 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!

Date: 2005-11-18 06:39 pm (UTC)
From: [identity profile] pphaneuf.livejournal.com
The trick part is also that with reiser, you might not necessarily want to run reiserfsck either.

Date: 2005-11-19 04:29 pm (UTC)
From: [identity profile] 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.

January 2017

S M T W T F S
1234567
891011121314
15161718192021
22232425262728
293031    

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jul. 4th, 2025 05:33 am
Powered by Dreamwidth Studios