From: Eric Sandeen <sandeen@sandeen.net>
To: hank peng <pengxihan@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>, xfs@oss.sgi.com
Subject: Re: XFS mount failuer on RAID5
Date: Fri, 16 Oct 2009 10:55:13 -0500 [thread overview]
Message-ID: <4AD89761.4000605@sandeen.net> (raw)
In-Reply-To: <4AD89128.2010206@sandeen.net>
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@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@Storage:~# mkdir tmp
>> root@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
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-10-16 15:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 3:09 XFS mount failuer on RAID5 hank peng
2009-10-16 8:19 ` Michael Monnerie
2009-10-16 15:27 ` Eric Sandeen
2009-10-17 21:27 ` Michael Monnerie
2009-10-19 1:30 ` Dave Chinner
2009-10-19 3:55 ` Christoph Hellwig
2009-10-16 8:30 ` Justin Piszcz
2009-10-16 15:28 ` Eric Sandeen
2009-10-16 15:55 ` Eric Sandeen [this message]
2009-10-19 0:54 ` hank peng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AD89761.4000605@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-raid@vger.kernel.org \
--cc=pengxihan@gmail.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox