Messages in this thread | | | Date | Sun, 19 Oct 2008 07:12:47 +0200 | From | Martin Michlmayr <> | Subject | Re: XFS filesystem corruption on the arm(el) architecture |
| |
* Dave Chinner <david@fromorbit.com> [2008-10-19 12:48]: > That's the log replay indicating that there's a bad transaction > header in the log. Very strange - it shoul dbe a clean log. What > does xfs_logprint -t /dev/sda5 tell you about the transactions > in the log?
mdebian:~# mkfs.xfs -f /dev/sda5 meta-data=/dev/sda5 isize=256 agcount=4, agsize=94380 blks = sectsz=512 attr=2 data = bsize=4096 blocks=377519, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 log =internal log bsize=4096 blocks=2560, version=2 = sectsz=512 sunit=0 blks, lazy-count=0 realtime =none extsz=4096 blocks=0, rtextents=0 debian:~# mount -t xfs /dev/sda5 /mnt debian:~# cp /usr/bin/* /mnt/ debian:~# umount /mnt debian:~# mount -t xfs /dev/sda5 /mnt mount: /dev/sda5: can't read superblock debian:~# xfs_logprint -t /dev/sda5 xfs_logprint: data device: 0x805 log device: 0x805 daddr: 1510112 length: 20480
XFS: Log inconsistent (didn't find previous header) XFS: empty log check failed xfs_logprint: failed to find head and tail, error: 5 debian:~#
-- Martin Michlmayr http://www.cyrius.com/
| |