xfs
[Top] [All Lists]

FS Corruption and Repair Path

To: <linux-xfs@xxxxxxxxxxx>
Subject: FS Corruption and Repair Path
From: "Walt H" <waltabbyh@xxxxxxxxxx>
Date: Sat, 17 Mar 2001 08:57:03 -0800
Delivered-to: fixup-linux-xfs@xxxxxxxxxxx@fixme
Sender: owner-linux-xfs@xxxxxxxxxxx
Hello,
 
I've been using XFS for a couple months now with very good results. However, last night had a couple of weird things happen. I pulled latest CVS and built a new kernel. In the process of shutting down the system for reboot into new kernel, the shutdown scripts stopped executing. The system was still up, however, and I was able to sync and emergency remount read-only prior to rebooting. The system successfully booted into the new kernel and all appeared well. After some time, another process got stuck so I proceeded to shutdown and boot off my repair disk to see if anything was wrong. xfs_check showed inconsistencies in the root FS, so I attempted to repair using xfs_repair. A number of problems existed and it attempted to repair them eventually failing with:
 
FATAL ERROR - XFS_CHECK    DUPLICATE INODE RANGE
 
(or something very close - typing up message from a diff machine)
 
No amount of fiddling on my part has been successful in getting past this error. I can still successfully mount this partition, however, there are damaged directory entries throughout. All the damaged entries are named "/ome" or some such where the first letter, "h" in this case is replaced with a leading slash. I've tried using xfs_db to step through it as well as xfs_ncheck to determine the files at this inode location (127069055) but can't find anything. Worst case, I can reformat this partition and reinstall, but would like to know what causes this and how to avoid it. This machine has locked up a couple times as of late (nvidia card w/ latest drivers, not so good) - Most of the time, I've been paranoid due to my newness to XFS and have fsck'd the FS from my repair boot disk w/o any errors showing up. Not sure what caused this?
 
Machine info:
P2 w/ 384MB ram, 2 IDE drives - partitioned as follows:
 
Maxtor 11.5GB - 4 partittions, connected to builtin IDE
hda1 = vfat32   approx. 7.5 GB
hda2 = ext2 (boot)  300 MB
hda3 = swap  250 MB
hda4 = xfs (/root)  remainder of drive
 
IBM Deskstar 15GB - 3 Partitions, connected to Promise UDMA 66
hde1 = vfat32  2 GB
hde2 = xfs (/home)  5 GB
hde3 = xfs (/usr)  remainder of drive
 
Interestingly, hde2 has no problems - and hde3 reports similar inconsistencies to hda4. I haven't attempted to repair it yet.
Any help would be greatly appreciated. Thanks.
 
Walt
<Prev in Thread] Current Thread [Next in Thread>
  • FS Corruption and Repair Path, Walt H <=