Log in

No account? Create an account

Josh-D. S. Davis

Xaminmo / Omnimax / Max Omni / Mad Scientist / Midnight Shadow / Radiation Master

Previous Entry Share Next Entry
Losing faith in Linux
Josh 201604 KWP
Years ago, I lost 36G due to an LVM issue. I couldn't even figure out what it was. The LVM 1.0 config just "went away" off of my RAID-5.

Today, I lost one spindle out of my RAID-6. It wasn't even a hard loss. It was a retry timeout. I decided to reboot.

I rebooted. Not a crash. No problems. Just a reboot. The system didn't come up. I had Erica power the machine on, and it came up to a ^D prompt for one filesystem. This filesystem was marked in fstab with "nofail", so it shouldn't have stopped the boot.

Whatever. ^D to continue and I'll mess with it in normal mode. Well, it was mounted in normal mode.

So I dismount it and run fsck. INFINITE ERRORS! fsck.ext4 begins scrubbing my filesystem of any useful information. It won't use any of the superblock backups either.

So I gave up after about 20 minutes of errors scrolling by. I mount it up and now it says 1% used. BAH!

It *looks* like all of my files are actually there, so I'm trying to copy them off to other places for inspection/salvage.

But this is unacceptable. RAID FUCKING SIX, one drive down. No other system problems, and I had no problems before the reboot. I just wanted to reset the spindle.

There is no reason for fsck.ext4 to scrub the entire filesystem of data. it looks like fsck.ext4 is the same program as for all other fsck.ext*, and it looks like it has no idea what ext4 really is.

So, not only did fsck not complete in a few minutes as it should with ext4, but it munged my filesystem.

THIS SHOULD NEVER HAPPEN, especially when I still had N+P in the RAID.

Of course, if I had run e2image prior to fsck, then I could restore the image; however, who is in the habit of running that? I just ran fsck and walked away. *sigh*

I cannot express how displeased I am with this.