It's not like I had a choice, the 4TB filesystem made of 10 x 500Gb SATA disks in RAID5 lost a disk and did a funky dance, and now it won't let anyone mount it except read only.
So I had to unmount it, with umount -l because when I tried plain old umount /name it said "device is busy". I don't know how it could be busy, I was the only person connected to the machine and no other server had it mounted...so I ran "umount -l /name" and that did the trick in about 20 seconds.
Then on to the fsck of the unmounted filesystem...did I mention it's 4 terabytes? What I would love to know...LOVE to know....is how long it takes to fsck a 4TB filesystem? A couple hours, a day, a weekend, or until eternity and the disks stop spinning?
I guess too if I had another wish it would be that there was some kind of moving blinking cursor to let me know fsck was doing something. After I said "yes" to a few dozen errors about block bitmaps, inode bitmaps, and inode tables with their ominous message "warning: severe data loss possible" then it spit out:
/dev/sdb contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
where it has sat for the last hour, completely unresponsive.
Am I missing something? Did I miss the prompt for verbose output???
Answers:
- there is a prompt for verbose output but it didn't help much
- fsck on a 4TB disk took about 6 hours with lots of errors
- there is a progress bar using -C but I couldn't get it to display, probably missed something
Finally I ran it as root in the background, sent output to a log file, and went to sleep.
No comments:
Post a Comment