From: Christoph Hellwig <hch@infradead.org>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs@oss.sgi.com
Subject: Re: XFS, NFS and inode64 on 2.6.27
Date: Sat, 21 Nov 2009 08:16:57 -0500 [thread overview]
Message-ID: <20091121131657.GA2095@infradead.org> (raw)
In-Reply-To: <200911201152.43809@zmi.at>
On Fri, Nov 20, 2009 at 11:52:43AM +0100, Michael Monnerie wrote:
> The shares "daten" and "dvd-images" can be mounted from other servers. I
> simply went to the original dirs of this mount-bind, and created several
> new dirs:
> mkdir 1 2 3 4 5 6 7 8 9
> and one of them had an inode < 2G, so I moved the contents there and
> renamed the dirs, remounted the --bind mounts and now have this:
So your NFS exports are not the roots of their respsective filesystems?
This means NFSD uses non-standard filesystem IDs in the filehandles
which have to encode the inode number of the export root. Your best
option is to simplify switch to exporting a whole filesystem,
alternatively you can try making sure NFSD uses the 16byte wide UUID
style export. Note thast either way will only work with a 64bit kernel
as the fs has no say in encoding the filesystem part of the handle
and ino_t is always 32bit on 32bit platforms. This will also affect
any other filesystem with 64bit inode numbers.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-11-21 13:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 10:52 XFS, NFS and inode64 on 2.6.27 Michael Monnerie
2009-11-20 21:23 ` Nathaniel W. Turner
2009-11-21 10:47 ` Michael Monnerie
2009-11-21 13:16 ` Christoph Hellwig [this message]
2009-11-21 21:17 ` Michael Monnerie
2009-11-22 12:31 ` Christoph Hellwig
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=20091121131657.GA2095@infradead.org \
--to=hch@infradead.org \
--cc=michael.monnerie@is.it-management.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox