Hey Kamal,
On Wed, Jan 23, 2013 at 12:35:09PM +1100, Dave Chinner wrote:
> On Tue, Jan 22, 2013 at 08:24:02PM -0500, Kamal Dasu wrote:
> > I am running a simple test with xfs_io on Kernel 3.3 writing in
> > O_DIRECT mode and I get
> >
> > # /rt.sh
> > ++ DEV=/dev/sda2
> > ++ RTDEV=/dev/sda3
> > ++ MNT=/mnt/xfsmnt
> > ++ mkdir /mnt/xfsmnt
> > ++ mkfs.xfs -f /dev/sda2 -r extsize=2m,rtdev=/dev/sda3
> > meta-data=/dev/sda2 isize=256 agcount=4, agsize=983479 blks
> > = sectsz=512 attr=2, projid32bit=0
> > data = bsize=4096 blocks=3933916, imaxpct=25
> > = sunit=0 swidth=0 blks
> > naming =version 2 bsize=4096 ascii-ci=0
> > log =internal log bsize=4096 blocks=2560, version=2
> > = sectsz=512 sunit=0 blks, lazy-count=1
> > realtime =/dev/sda3 extsz=2097152 blocks=240089416,
> > rtextents=468924
>
> Patches are pending in 3.8 to fix the oops, but it won't fix your
> problems.....
Here is the patch Dave is referring to.
http://oss.sgi.com/archives/xfs/2013-01/msg00323.html
It prevents xfs_perag_get returning a null pag.
Regards,
Ben
|