xfs
[Top] [All Lists]

Re: XFS on 2.4 Tib raid

To: lvismer@xxxxxxxxxxxxxxxx
Subject: Re: XFS on 2.4 Tib raid
From: Dave Chinner <dgc@xxxxxxx>
Date: Wed, 11 May 2005 08:44:50 +1000
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <1115712231.42806ae75b4d1@picturenet.co.za>; from lvismer@picturenet.co.za on Tue, May 10, 2005 at 10:03:51AM +0200
References: <200505092210.25667.lvismer@picturenet.co.za> <200505100656.20204.lvismer@picturenet.co.za> <200505101008.47081.naude@picturenet.co.za> <1115712231.42806ae75b4d1@picturenet.co.za>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5.1i
On Tue, May 10, 2005 at 10:03:51AM +0200, lvismer@xxxxxxxxxxxxxxxx wrote:
> > > I am using an ATTO scsi card speaking to an Infortrend 2.4 Tib raid
> > > system.
> > >
> > > I created a filesystem using:
> > > mkfs.xfs -L iftraid -f /dev/sdc

So you haven't created a partition table on the device at all?

> > What's the actual error? This is the stack trace that's part of the
> > error message, but does not inidcate what the error was. Can you
> > include the error messages that were emitted before the stack trace?
> >
> I include the full error from /var/log/messages. As one copies
> files it stops at some point and the following error loops and the
> machine needs to be rebooted.
> 
> 0x0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> Filesystem "sdc": XFS internal error xfs_alloc_read_agf at line 2195 of file 
> fs/
> xfs/xfs_alloc.c.  Caller 0xd0b638ca
>  [<d0b63ced>] xfs_alloc_read_agf+0x12d/0x1f0 [xfs]
>  [<d0b638ca>] xfs_alloc_fix_freelist+0x47a/0x490 [xfs]
>  [<d0b6407d>] xfs_alloc_vextent+0x2cd/0x500 [xfs]

So we're trying to allocate an extent and the AGF read from disk
is full of zeros.

Can you do the following:

        - write a known pattern to the disk before making the
          filesystem (0xa5 is a good one)
        - make the filesystem
        - run xfs_check on the device before mounting to validate
          the filesystem was made properly
        - mount the filesystem
        - run your copy until it breaks
        - run xfs_check on the filesystem (if you needed to reboot
          to get here, you should mount and unmount the filesystem
          to replay the log first)
        - run xfs_repair on the filesystem if xfs_check finds
          errors

And post the output of any errors that are found?

If there really is a AGF full of zeros (or 0xa5!) in the filesystem,
xfs_check will find it.

BTW, did you build the kernel with CONFIG_LBD=y (i.e. support block
devices larger than 2TiB)?

Cheers,

Dave.
-- 
Dave Chinner
R&D Software Engineer
SGI Australian Software Group


<Prev in Thread] Current Thread [Next in Thread>