public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Krzysztof Adamski" <k@adamski.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: NFS export broke with change from ext3 to xfs
Date: Tue, 5 Jan 2010 12:21:49 -0500 (EST)	[thread overview]
Message-ID: <43686.205.189.93.240.1262712109.squirrel@webmail.netxsys.com> (raw)
In-Reply-To: <4B437240.3030902@sandeen.net>

> Krzysztof Adamski wrote:
>> 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.
>
> I dunno, this should work.  Anything in either of the system logs?

On the server:
Jan  4 19:27:03 Myth mountd[5342]: authenticated mount request from
x.x.x.x:741 for /file-store/nfs-roots/f1/var
(/file-store/nfs-roots/f1/var)
Jan  4 19:27:03 Myth mountd[5342]: authenticated mount request from
x.x.x.x:757 for /file-store/nfs-roots/f1/usr
(/file-store/nfs-roots/f1/usr)
Jan  4 19:27:03 Myth mountd[5342]: authenticated mount request from
x.x.x.x:759 for /file-store/nfs-roots/f1/home
(/file-store/nfs-roots/f1/home)
but this is identical to when it worked.
No logs on the client, /var is not yet mounted.

Should I be asking on the NFS list?


> -Eric
>
>> 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
>>
>

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-01-05 17:21 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 [this message]
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=43686.205.189.93.240.1262712109.squirrel@webmail.netxsys.com \
    --to=k@adamski.org \
    --cc=sandeen@sandeen.net \
    --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