I am new to this sys admin stuff so I would appreciate some info from those in the know. I am trying to do a repair on "/" which is the mount point for an XFS partition /dev/hda4. I have tried doing an "init S" to startup in single user but I am still unable to umount /. I have also tried mounting / as ro. Still can't do an xfs_repair. How can I perform an xfs_repair on /dev/hda4 (i.e. /)? What is the proper procedure for doing this? Here is the ouput from xfs_check -s /dev/hda4 : cormhouse:~ # xfs_check -s /dev/hda4 bad magic number 0x5b44 for inode 79835552 bad magic number 0 for inode 79835553 bad magic number 0 for inode 79835554 bad magic number 0 for inode 79835555 bad magic number 0 for inode 79835556 bad magic number 0 for inode 79835557 bad magic number 0 for inode 79835558 bad magic number 0 for inode 79835559 bad magic number 0 for inode 79835560 bad magic number 0 for inode 79835561 bad magic number 0 for inode 79835562 bad magic number 0 for inode 79835563 bad magic number 0 for inode 79835564 bad magic number 0 for inode 79835565 bad magic number 0 for inode 79835566 bad magic number 0 for inode 79835567 bad magic number 0x5b44 for inode 79835568 bad magic number 0x6c65 for inode 79835569 bad magic number 0x6269 for inode 79835570 bad magic number 0x6f76 for inode 79835571 bad magic number 0 for inode 79835572 bad magic number 0 for inode 79835573 bad magic number 0 for inode 79835574 bad magic number 0 for inode 79835575 bad magic number 0 for inode 79835576 bad magic number 0 for inode 79835577 bad magic number 0 for inode 79835578 bad magic number 0 for inode 79835579 bad magic number 0 for inode 79835580 bad magic number 0 for inode 79835581 bad magic number 0 for inode 79835582 bad magic number 0 for inode 79835583 /usr/sbin/xfs_check: line 63: 2780 Segmentation fault xfs_db$ISFILE -i -p xfs_check -c "check$OPTS" $1 And here is a snippet from xfs_repair -n /dev/hda4 : cormhouse:~ # xfs_repair -n /dev/hda4 Phase 1 - find and verify superblock... Phase 2 - using internal log - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... error following ag 12 unlinked list - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 imap claims in-use inode 46321751 is free, would correct imap imap claims in-use inode 46321752 is free, would correct imap - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - agno = 17 - agno = 18 - agno = 19 <snip> bad magic number 0x6269 on inode 79835570 bad version number 0x20 on inode 79835570 bad (negative) size -6236629774229475995 on inode 79835570 bad magic number 0x6f76 on inode 79835571 bad version number 0x0 on inode 79835571 bad inode format in inode 79835571 <snip> ------ Hope this long post doesn't put a rock in anyones craw. I am desperate for answers. TIA, Darrell Cormier
On Friday 06 June 2003 23.16, Darrell Cormier wrote:
How can I perform an xfs_repair on /dev/hda4 (i.e. /)? What is the proper procedure for doing this?
Standard procedure for repairing the root file system I think is to boot from the rescue system on the suse CD. That will boot up into a system running with / on a ram disk, so the real hard drive is unmounted. There could be other ways I guess, but that's the way I always do it
Anders Johansson wrote:
On Friday 06 June 2003 23.16, Darrell Cormier wrote:
How can I perform an xfs_repair on /dev/hda4 (i.e. /)? What is the proper procedure for doing this?
Standard procedure for repairing the root file system I think is to boot from the rescue system on the suse CD. That will boot up into a system running with / on a ram disk, so the real hard drive is unmounted.
There could be other ways I guess, but that's the way I always do it
Thanks Anders. That did the trick. Darrell
participants (2)
-
Anders Johansson
-
Darrell Cormier