sneezewort
asked on
Can't read my XFS
I have 2 raid5 arrays that are tied together using LVM. and XFS, so both raids were mounted as /data.
Here is my fstab entry:
/dev/mapper/VolumeGroup01- DataVolume /data xfs noatime 0 2
I had problems rebuilding the raid so 3-ware sent me a scritp and it repaired the raid, but when I booted into the OS (debian) I was able to browse to /data and do an ls. I could see the directory contents and all seemd fine. I then did an ls a few seconds later and recieved:
ls: reading directory .: Input/output error
I looked in the dmesg logs and found:
xfs_force_shutdown(dm-0,0x 8) called from line 1139 of file fs/xfs/xfs_trans.c. Return address = 0xf8cb7708
Filesystem "dm-0": Corruption of in-memory data detected. Shutting down filesystem: dm-0
Please umount the filesystem, and rectify the problem(s)
Ending XFS recovery on filesystem: dm-0 (logdev: internal)
xfs_force_shutdown(dm-0,0x 1) called from line 424 of file fs/xfs/xfs_rw.c. Return address = 0xf8cb7708
xfs_force_shutdown(dm-0,0x 1) called from line 424 of file fs/xfs/xfs_rw.c. Return address = 0xf8cb7708
Can anyone please help me get my data off this thing?
Here is my fstab entry:
/dev/mapper/VolumeGroup01-
I had problems rebuilding the raid so 3-ware sent me a scritp and it repaired the raid, but when I booted into the OS (debian) I was able to browse to /data and do an ls. I could see the directory contents and all seemd fine. I then did an ls a few seconds later and recieved:
ls: reading directory .: Input/output error
I looked in the dmesg logs and found:
xfs_force_shutdown(dm-0,0x
Filesystem "dm-0": Corruption of in-memory data detected. Shutting down filesystem: dm-0
Please umount the filesystem, and rectify the problem(s)
Ending XFS recovery on filesystem: dm-0 (logdev: internal)
xfs_force_shutdown(dm-0,0x
xfs_force_shutdown(dm-0,0x
Can anyone please help me get my data off this thing?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Perhaps it's just a corrupt filesystem that can be fixed.