XFS mount failuer on RAID5
Eric Sandeen
sandeen at sandeen.net
Fri Oct 16 10:55:13 CDT 2009
Eric Sandeen wrote:
> hank peng wrote:
>> Hi, all:
>> I have a self-built board, cpu is MPC8548(PPC arch), kernel is based
>> on MPC8548CDS demo board, version is 2.6.23.
>> A SATA controller is conected to CPU via PCIX, and I have 3 disks
>> attached to it.
>>
> ...
>
>> root at Storage:~# mkfs.xfs -f -ssize=4k /dev/vg/lvtest
>> Warning - device mapper device, but no dmsetup(8) found
>> Warning - device mapper device, but no dmsetup(8) found
>> meta-data=/dev/vg/lvtest isize=256 agcount=4,
>> agsize=6553600 blks
>> = sectsz=4096 attr=2
>> data = bsize=4096 blocks=26214400, imaxpct=25
>> = sunit=0 swidth=0 blks
>> naming =version 2 bsize=4096
>> log =internal log bsize=4096 blocks=12800, version=2
>> = sectsz=4096 sunit=1 blks, lazy-count=0
>> realtime =none extsz=4096 blocks=0, rtextents=0
>> root at Storage:~# mkdir tmp
>> root at Storage:~# mount -t xfs /dev/vg/lvtest ./tmp/
>> Filesystem "dm-0": Disabling barriers, not supported by the underlying
>> device
>> XFS mounting filesystem dm-0
>> XFS: totally zeroed log
>> Filesystem "dm-0": XFS internal error xlog_clear_stale_blocks(2) at
>> line 1252 of file fs/xfs/xfs_log_recover.c. Caller 0xc018ec88
>
>
> Can you try the patch that Andy Poling posted to the list just
> yesterday? Slight longshot but it may be it.
>
> Otherwise I will look at this in a bit; on the road today though.
>
> -Eric
Actually you might try a newer xfsprogs and/or kernel; if I do this on a
loopback file, creating the same geometry as you have:
mkfs.xfs -dfile,name=fsfile,size=2621440b -lsize=12800b,lazy-count=0
-ssize=4096
it mounts fine w/ latest xfsprogs and a 2.6.30 kernel.
-Eric
More information about the xfs
mailing list