Bug#508492: linux-image-2.6.26-1-parisc64: [hppa64] XFS internal error xlog_valid_rec_header(2)
On Thu, Dec 11, 2008 at 12:55:22PM -0700, Bryan Stillwell wrote:
> Package: linux-image-2.6.26-1-parisc64
> Version: 2.6.26-11
> Severity: important
>
> When attempting to use XFS on /dev/sdb1 on an HP Visualize C3650, I'm
> seeing problems with very basic usage:
> -----------------------------------------------------------------------
> noriko:~# mkfs.xfs /dev/sdb1 -f
> meta-data=/dev/sdb1 isize=256 agcount=4, agsize=1111423 blks
> = sectsz=512 attr=2
> data = bsize=4096 blocks=4445692, 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
> noriko:~# mount /dev/sdb1 /mnt/
> noriko:~# cd /mnt
> noriko:/mnt# cp /usr/bin/* .
> cp: omitting directory `/usr/bin/X11'
> noriko:/mnt# cd
> noriko:~# umount /mnt
> noriko:~# mount /dev/sdb1 /mnt/
> mount: Structure needs cleaning
> -----------------------------------------------------------------------
>
>
> The output from dmesg points at an XFS internal error in log recovery:
> -----------------------------------------------------------------------
> [17179748.064000] XFS mounting filesystem sdb1
> [17179748.268000] Starting XFS recovery on filesystem: sdb1 (logdev: internal)
> [17179748.280000] Filesystem "sdb1": XFS internal error xlog_valid_rec_header(2) at line 3486 of file fs/xfs/xfs_log_recover.c. Caller 0x000000000076ad34
> [17179748.288000] Backtrace:
> [17179748.292000] [<0000000040115b24>] show_stack+0x14/0x20
> [17179748.296000] [<0000000040115b48>] dump_stack+0x18/0x28
> [17179748.304000] [<00000000007500cc>] xfs_error_report+0x54/0x60 [xfs]
> [17179748.308000] [<0000000000766cec>] xlog_valid_rec_header+0xf4/0x108 [xfs]
> [17179748.316000] [<000000000076ad34>] xlog_do_recovery_pass+0xec/0x830 [xfs]
> [17179748.320000] [<000000000076b4d4>] xlog_do_log_recovery+0x5c/0xd0 [xfs]
> [17179748.328000] [<000000000076b56c>] xlog_do_recover+0x24/0x190 [xfs]
> [17179748.332000] [<000000000076b788>] xlog_recover+0xb0/0xd8 [xfs]
> [17179748.340000] [<0000000000763a50>] xfs_log_mount+0x100/0x170 [xfs]
> [17179748.344000] [<000000000076d708>] xfs_mountfs+0x398/0x828 [xfs]
> [17179748.348000] [<0000000000775938>] xfs_mount+0x338/0x450 [xfs]
> [17179748.356000] [<0000000000789f34>] xfs_fs_fill_super+0x10c/0x330 [xfs]
> [17179748.360000] [<00000000401aa710>] get_sb_bdev+0x198/0x238
> [17179748.368000] [<0000000000787cb8>] xfs_fs_get_sb+0x20/0x30 [xfs]
> [17179748.372000] [<00000000401a9fc8>] vfs_kern_mount+0xe0/0x1e8
> [17179748.380000] [<00000000401aa160>] do_kern_mount+0x68/0x148
> [17179748.384000]
> [17179748.388000] XFS: log mount/recovery failed: error 177
> [17179748.396000] XFS: log mount failed
> -----------------------------------------------------------------------
Does this still occur with later kernels, such as 2.6.30 from unstable
or backports.org?
Cheers,
Moritz
Reply to: