From: Lukas Hejtmanek <xhejtman@ics.muni.cz>
To: linux-nfs@vger.kernel.org
Subject: 64bit inodes and IA32 apps over NFS
Date: Fri, 13 Aug 2010 16:47:03 +0200 [thread overview]
Message-ID: <20100813144703.GP20901@ics.muni.cz> (raw)
Hello,
is there any workaround for NFSv4 when exporting XFS with 64bit inodes?
IA32 apps receives:
getdents(3, 0xb7571008, 1000) =3D -1 EOVERFLOW (Value too lar=
ge for defined data type)
when compiling on x86_64, I got not error.
=46rom the XFS man page:
By default, with 32bit inodes, XFS places inodes only in the first 1TB =
of
a disk. If you have a disk with 100TB, all inodes will be stuck in the =
first
TB. This can lead to strange things like "disk full" when you still hav=
e
plenty space free, but there's no more place in the first TB to create =
a new
inode. Also, performance sucks.
To come around this, use the inode64 mount options for filesystems >1TB=
=2E
Inodes will then be placed in the location where their data is, minimiz=
ing
disk seeks.
Beware that some old programs might have problems reading 64bit inodes,
especially over NFS.
So, is there any workaround in NFS for IA32 apps?
--=20
Luk=E1=B9 Hejtm=E1nek
next reply other threads:[~2010-08-13 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 14:47 Lukas Hejtmanek [this message]
2010-08-15 0:58 ` 64bit inodes and IA32 apps over NFS Trond Myklebust
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=20100813144703.GP20901@ics.muni.cz \
--to=xhejtman@ics.muni.cz \
--cc=linux-nfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).