From: Christoph Hellwig <hch@infradead.org>
To: hank peng <pengxihan@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>, linux-xfs@oss.sgi.com
Subject: Re: stale NFS file handle problem on XFS inode64
Date: Tue, 22 Nov 2011 17:15:15 -0500 [thread overview]
Message-ID: <20111122221515.GA29540@infradead.org> (raw)
In-Reply-To: <CAJNJY8Ty+bQpzGL9wq7Qv3ozcKUPwmTyYUeb2wQqZ326K4JeWw@mail.gmail.com>
On Tue, Nov 22, 2011 at 08:19:15AM +0800, hank peng wrote:
> > Do you export the root directory of the XFS filesystem, or a
> > subdirectory in it? ??If it's the former it should work in theory,
> > althrough I'm not sure how well 64-bit inode numbers work with a client
> > that old, if it's the latter it needs a few tweaks to work, see
> >
> The following is what I did:
> 1. mkfs.xfs /dev/sdb (whole disk)
> 2. create a mount point in my root filesystem:
> mkdir /mnt/mymount
> 3. monut xfs with inode64
> mount /dev/sdb /mnt/mymount -o inode64
> 4. export it in NFS /etc/exports
> /mnt/mymount *(rw, no_root,squash, sync)
>
> so, is there any problem here?
That should work fine, and I've tried it a lot of times. Do you see
the same issue when mounting the fs on the server (not recommended for
production use, just for testing!) and accessing it from the 2.6.35
kernel nfs client?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-11-22 22:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 13:00 stale NFS file handle problem on XFS inode64 hank peng
2011-11-21 14:01 ` Emmanuel Florac
2011-11-21 15:02 ` hank peng
2011-11-21 15:21 ` Emmanuel Florac
2011-11-21 15:28 ` hank peng
2011-11-21 15:43 ` Emmanuel Florac
2011-11-22 7:14 ` hank peng
2011-11-21 17:04 ` Christoph Hellwig
2011-11-22 0:19 ` hank peng
2011-11-22 1:46 ` Dave Chinner
2011-11-22 3:22 ` hank peng
2011-11-22 20:35 ` Emmanuel Florac
2011-11-22 22:16 ` Christoph Hellwig
2011-11-22 22:15 ` Christoph Hellwig [this message]
2011-11-23 1:19 ` hank peng
2011-11-28 11: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=20111122221515.GA29540@infradead.org \
--to=hch@infradead.org \
--cc=linux-xfs@oss.sgi.com \
--cc=pengxihan@gmail.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