From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Christoph Hellwig <hch@infradead.org>,
Samuel Kvasnica <samuel.kvasnica@ims.co.at>
Subject: Re: [PATCH] xfs: fix exporting with left over 64-bit inodes
Date: Sat, 20 Nov 2010 09:29:06 +0100 [thread overview]
Message-ID: <201011200929.08113@zmi.at> (raw)
In-Reply-To: <20101119133848.GA5471@infradead.org>
[-- Attachment #1.1: Type: Text/Plain, Size: 943 bytes --]
On Freitag, 19. November 2010 Christoph Hellwig wrote:
> We now support mounting and using filesystems with 64-bit inodes even
> when not mounted with the inode64 option (which now only controls if
> we allocate new inodes in that space or not). Make sure we always
> use large NFS file handles when exporting a filesystem that may
> contain 64-bit inodes. Note that this only affects newly generated
> file handles, any outstanding 32-bit file handle is still accepted.
Could that help with the problem of not being able to mount an NFS share
when the top shared dir itself is a 64bit inode?
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
// ****** Radiointerview zum Thema Spam ******
// http://www.it-podcast.at/archiv.html#podcast-100716
//
// Haus zu verkaufen: http://zmi.at/langegg/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-11-20 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 13:38 [PATCH] xfs: fix exporting with left over 64-bit inodes Christoph Hellwig
2010-11-20 8:29 ` Michael Monnerie [this message]
2010-11-21 10:57 ` Christoph Hellwig
2010-11-22 0:37 ` Dave Chinner
2010-11-22 9:05 ` Samuel Kvasnica
2010-11-22 10:23 ` 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=201011200929.08113@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=hch@infradead.org \
--cc=samuel.kvasnica@ims.co.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