[Top] [All Lists]

Re: XFS: can't read superblock

To: Mathieu GOMBAULT <qwerty@xxxxxxxxx>
Subject: Re: XFS: can't read superblock
From: Eric Sandeen <sandeen@xxxxxxx>
Date: Sat, 20 Nov 2004 09:26:31 -0600
Cc: evilninja <evilninja@xxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <419F27B7.10803@xxxxxxxxx>
References: <419F1985.9010603@xxxxxxxxx> <419F1896.6020501@xxxxxxx> <419F27B7.10803@xxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.9 (Macintosh/20041103)
Mathieu GOMBAULT wrote:

here are all the logs I made:

qwerty@Pegasus:~$;-) sudo xfs_repair -v /dev/hdd1

Looks like xfs_repair found nothing wrong...

qwerty@Pegasus:~$;-) cat /proc/partitions
major minor  #blocks  name

22    64  160086528 hdd
22    65  159993460 hdd1

A little odd that hdd1 is smaller than hdd?

qwerty@Pegasus:~$;-)sudo strace -omount.trace mount -t xfs /dev/hdd1 /mnt
mount: /dev/hdd1: can't read superblock

qwerty@Pegasus:~$;-) sudo mount -t xfs /dev/hdd1 /mnt/
mount: /dev/hdd1: can't read superblock
qwerty@Pegasus:~$;-) dmesg | tail
I/O error in filesystem ("hdd1") meta-data dev hdd1 block 0x1314ff7f ("xfs_read_buf") error 5 buf count 512
XFS: size check 2 failed
attempt to access beyond end of device

size check 2 tries to read the last block on the disk. It's saying it cant' read block 0x1314ff74 which is block 320143231 (in 512b blocks, or 160071615 in 1k blocks - which is past the end of hdd1 but still on hdd)

I'd either remove the size check 2 and rebuild xfs, then mount read-only and copy the data somewhere safe.... or if you're feeling brave, extend hdd1 to the end of your disk using your favorite partition editor.

not sure how this happened...


<Prev in Thread] Current Thread [Next in Thread>