From: Emmanuel Florac <eflorac@intellique.com>
To: xfs@oss.sgi.com
Subject: Re: NFS export broke with change from ext3 to xfs
Date: Tue, 5 Jan 2010 21:37:14 +0100 [thread overview]
Message-ID: <20100105213714.5b9b2a11@galadriel.home> (raw)
In-Reply-To: <20100105174332.GA14496@infradead.org>
Le Tue, 5 Jan 2010 12:43:32 -0500 vous écriviez:
> Remove the inode64 mount option or move every export to a separate
> filesystem. The NFS code can't cope with 64 bit inode numbers when
> exporting a subtree of a filesystem. You'd see the same issue with
> e.g. ocfs2 or gfs2.
Does the kernel architecture (32 or 64 bits) have any influence there?
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-01-05 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 0:48 NFS export broke with change from ext3 to xfs Krzysztof Adamski
2010-01-05 17:09 ` Eric Sandeen
2010-01-05 17:21 ` Krzysztof Adamski
2010-01-05 17:43 ` Christoph Hellwig
2010-01-05 20:37 ` Emmanuel Florac [this message]
2010-01-06 18:09 ` 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=20100105213714.5b9b2a11@galadriel.home \
--to=eflorac@intellique.com \
--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