From: Krzysztof Adamski <k@adamski.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: XFS: file system too large to be mounted on this system. 2.6.30.1
Date: Thu, 23 Jul 2009 20:25:30 -0400 [thread overview]
Message-ID: <1248395130.4520.3.camel@oxygen.netxsys.com> (raw)
In-Reply-To: <4A67E4DE.1050904@sandeen.net>
On Wed, 2009-07-22 at 23:19 -0500, Eric Sandeen wrote:
> Krzysztof Adamski wrote:
> > I got "XFS: file system too large to be mounted on this system." when
> > mounting my not to large file system.
> >
> > I'm running Debian lenny with a self compiled kernel, 32 bit userland
> > distribution.
> >
> > I have both 32 and 64 bit kernels of the 2.6.30.1 installed. I was
> > running the 64bit kernel for a while, I needed to switch to the 32 bit
> > version to run VBox. After reboot to 32bit kernel, one filesystem would
> > not mount. The xfs_repair did not find any good superblocks.
> > Fortunately booting the 64bit kernel allowed mounting of this
> > filesystem.
> > This is a df while running 64bit kernel:
> > /dev/mapper/big--raid-file--store
> > xfs 2558652416 2540114040 18538376 100% /file-store
> > /dev/sda1 xfs 195263012 194723636 539376 100% /disks/a1
> >
> > The interesting part is that /disks/a1 did not have problem with
> > mounting on the 32bit kernel, just the /file-store.
>
>
> Do you have CONFIG_LBD (or maye now CONFIG_LBDAF) set on the newer
> 32-bit kernel? You'll need that.
Yes, this was it, the CONFIG_LBD got unset when I used the .config file
to compile on a system that was running a 64 bit kernel. Now everything
is back to normal, thanks.
>
> If you do ....
>
> file-store is about 2T? What is the filesystem block size? (xfs_info
> on the mountpoint would tell you)
For reference:
# xfs_info /file-store
meta-data=/dev/mapper/big--raid-file--store isize=256 agcount=32,
agsize=19990496 blks
= sectsz=512 attr=0
data = bsize=4096 blocks=639695872,
imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096
log =internal bsize=4096 blocks=32768, version=1
= sectsz=512 sunit=0 blks, lazy-count=0
realtime =none extsz=65536 blocks=0, rtextents=0
>
> The test is looking at whether the nr of filesystem blocks overflows
> based on CONFIG_LBD or not...
>
> and the function hasn't changed since 2007.... hrm.
>
> I'll put my money on CONFIG_LBDAF.
>
> -Eric
>
> > When running 2.6.28.4 32bit kernel I have no problem with mounting this
> > filesystem. So something broke between 2.6.28.4 and 2.6.30.1
> >
> > I can provide any other info.
> >
> > K
> >
> >
> > _______________________________________________
> > xfs mailing list
> > xfs@oss.sgi.com
> > http://oss.sgi.com/mailman/listinfo/xfs
> >
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-07-24 0:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 1:41 XFS: file system too large to be mounted on this system. 2.6.30.1 Krzysztof Adamski
2009-07-23 4:19 ` Eric Sandeen
2009-07-24 0:25 ` Krzysztof Adamski [this message]
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=1248395130.4520.3.camel@oxygen.netxsys.com \
--to=k@adamski.org \
--cc=sandeen@sandeen.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.