From: Bernd Schubert <bernd-schubert@gmx.de>
To: linux-xfs@oss.sgi.com
Subject: Re: XFS "no space left" problem
Date: Mon, 05 Feb 2007 18:58:04 +0100 [thread overview]
Message-ID: <eq7r7c$b1n$1@sea.gmane.org> (raw)
In-Reply-To: 20070203233828.GD44411608@melbourne.sgi.com
David Chinner wrote:
> Or get a 64bit machine and use inode64. ;)
David, can you tell more in detail what you mean with "use inode64"?
We also just migrated our server to xfs, the largest partition has a size of
4TB. Lets say in the future a problem occurs and we could solve this by a
64-bit system? Migrating to 64-bit wouldn't be difficult, since the server
systems are already opterons. Only since we never bothered to migrate the
installation to x86_64 its not 64-bit yet. Would we need to tell xfs
somehow that it update its internal values to 64-bit integers or will it do
that automatically?
Btw, if you need 64-bit integers, why don't you use long long, or even
better with C99 int64_t?
Thanks,
Bernd
next prev parent reply other threads:[~2007-02-05 18:00 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 [this message]
2007-02-05 18:28 ` Eric Sandeen
2007-02-05 21:59 ` Bernd Schubert
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='eq7r7c$b1n$1@sea.gmane.org' \
--to=bernd-schubert@gmx.de \
--cc=linux-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox