From: Bernd Schubert <bernd-schubert@gmx.de>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs@oss.sgi.com
Subject: Re: XFS "no space left" problem
Date: Mon, 5 Feb 2007 22:59:47 +0100 [thread overview]
Message-ID: <200702052259.48018.bernd-schubert@gmx.de> (raw)
In-Reply-To: <45C7775F.9070408@sandeen.net>
On Monday 05 February 2007 19:28, you wrote:
> Bernd Schubert wrote:
> > David Chinner wrote:
> xfs is generally fully 64 bit, even on a 32 bit machine. see more below...
>
> > Btw, if you need 64-bit integers, why don't you use long long, or even
> > better with C99 int64_t?
>
> 32-bit machines can only do 32-bit inodes (vfs limitation) (at least
> 'til recently), so by default xfs doesn't let inode numbers go above 32
> bits - even though -internally- it -does- use a 64-bit container.
Ah, I see, linux vfs limitation.
>
> The xfs inode number encodes its location on disk, so this restriction
> also restricts which blocks can be allocated as inodes.
>
> xfs tries to reserve enough of these low blocks that you won't run out
> of potential inode blocks, but i've seen that get sideways. The
> original poster probably ran into trouble because he started with a 100G
> filesystem & grew it 10 or so times.
Well, we just also switched to a new raid device and before we bought it, we
also made sure its possible to do an online expansion. So a migration from 6
TB to 12 TB will come... I guess in two or three years.
>
> if you mount with inode64 you'll allow inodes to be allocated with more
> than 32 bits set. But this can only work on a 64 bit machine.
Ah, its a mount option! And even undocumented in "man 8 mount". Thanks will
add this to our wiki and write a debian bugreport.
>
> and then you have to be sure your userspace can cope w/ 64 bit inode
> numbers too.
Hmm, sizeof(ino_t) is 4 on x86_32, that will be a problem. We do have quite a
lot of programs, not written very well and not compilable with recent
compilers. On the other side, the linux nfs client converts inode numbers to
32 bit, if it would cause an overflow. However, it doesn't do that on x86_64
for 32bit programs. I know that quite well, due to another problem.
Thanks a lot for your insights,
Bernd
--
Bernd Schubert
PCI / Theoretische Chemie
Universität Heidelberg
INF 229
69120 Heidelberg
prev parent reply other threads:[~2007-02-05 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-03 18:37 XFS "no space left" problem wildcat
2007-02-03 23:38 ` David Chinner
2007-02-05 17:58 ` Bernd Schubert
2007-02-05 18:28 ` Eric Sandeen
2007-02-05 21:59 ` Bernd Schubert [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=200702052259.48018.bernd-schubert@gmx.de \
--to=bernd-schubert@gmx.de \
--cc=linux-xfs@oss.sgi.com \
--cc=sandeen@sandeen.net \
/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