From: Krzysztof Adamski <k@adamski.org>
To: xfs@oss.sgi.com
Subject: NFS export broke with change from ext3 to xfs
Date: Mon, 04 Jan 2010 19:48:20 -0500 [thread overview]
Message-ID: <1262652500.24160.27.camel@oxygen.netxsys.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1210 bytes --]
Hi All,
I just changed one filesystem on my mythbox from ext3 to xfs, and now I
can't get a client machine to NFS mount from it.
This is the export file on the server:
/file-store/nfs-roots/f1/home
f1(rw,no_root_squash,sync,no_subtree_check)
/file-store/nfs-roots/f1/usr
f1(rw,no_root_squash,sync,no_subtree_check)
/file-store/nfs-roots/f1/var
f1(rw,no_root_squash,sync,no_subtree_check)
and on the client(f1) the three filesystems are mount on /home, /usr,
and /var
This worked fine when /file-store on the server was formatted with ext3,
now that it is formatted with xfs I get this message on the client:
mount.nfs: Stale NFS file handle
I get this message 3 times.
Nothing else changed, both systems are Debian Lenny with custom kernel.
Server is 2.6.28, client is 2.6.29.6. NFS is version 3.
The fstab on the server has this:
/dev/mapper/big--raid-file--store /file-store xfs
noatime,logbsize=256k,inode64 0 1
The reason for the change of the filesystem was an upgrade of the drives
in the RAID, now the filesystem is 7T instead of 2.4T,
nothing else was changed. Why did this work with ext3 and does not with
XFS? What can I do to get this to work, short of reverting to ext3?
K
[-- Attachment #1.2: Type: text/html, Size: 1737 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-01-05 0:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 0:48 Krzysztof Adamski [this message]
2010-01-05 17:09 ` NFS export broke with change from ext3 to xfs Eric Sandeen
2010-01-05 17:21 ` Krzysztof Adamski
2010-01-05 17:43 ` Christoph Hellwig
2010-01-05 20:37 ` Emmanuel Florac
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=1262652500.24160.27.camel@oxygen.netxsys.com \
--to=k@adamski.org \
--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