Re: xfs_check - out of memory | xfs_repair - superblock error reading

[Stephan Jansen <jansen@xxxxxxxxxxxxxx>]

Hi,


On Sep 18, 2006, at 5:23 PM, David Chinner wrote:

> On Mon, Sep 18, 2006 at 03:19:18PM +0200, christian gattermair wrote:
> > hi!
> >
> > after a reboot of our box (debian sarge, 3ware controller, raid 5  
> > - 3tb xfs)
> > we can not mount it any more.
> >
> > from syslog:
> >
> > Sep 18 12:51:36 localhost kernel: SGI XFS with ACLs, security  
> > attributes,
> > realtime, large block numbers, no debug enabled
> > Sep 18 12:51:36 localhost kernel: SGI XFS Quota Management subsystem
> > Sep 18 12:51:53 localhost kernel: attempt to access beyond end of  
> > device
> > Sep 18 12:51:53 localhost kernel: sdb1: rw=0, want=6445069056,
> > limit=2150101796
> > Sep 18 12:51:53 localhost kernel: I/O error in filesystem ("sdb1")  
> > meta-data
> > dev sdb1 block 0x18027f2ff       ("xfs_read_buf") error 5 buf  
> > count 512
> > Sep 18 12:51:53 localhost kernel: XFS: size check 2 failed
> I/O error - something is not right with your raid controller i think.
> Are there any other errors in dmesg? What does /proc/partitions tell
> you about the size of the device?
>
> > xfs_check fails with:
> >
> > xfs_check /dev/sdb1
> > XFS: totally zeroed log
> > xfs_check: out of memory
> 3TB filesystem - you won't be able to xfs_check that on a 32 bit  
> system,
> and you'll need >6GiB RAM to check it on a 64bit system.
I was just going to create a 3TB filesystem on a 32 bit system.  So
xfs_check will not work?  How about xfs_repair?  I assume that will
work but would like to know beforehand.

[stuff deleted]

> Cheers,
>
> Dave.
> --
> Dave Chinner
> Principal Engineer
> SGI Australian Software Group
--

----- Stephan

smime.p7s
Description: S/MIME cryptographic signature