* NFS export broke with change from ext3 to xfs
@ 2010-01-05 0:48 Krzysztof Adamski
2010-01-05 17:09 ` Eric Sandeen
2010-01-05 17:43 ` Christoph Hellwig
0 siblings, 2 replies; 6+ messages in thread
From: Krzysztof Adamski @ 2010-01-05 0:48 UTC (permalink / raw)
To: xfs
[-- 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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: NFS export broke with change from ext3 to xfs
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
1 sibling, 1 reply; 6+ messages in thread
From: Eric Sandeen @ 2010-01-05 17:09 UTC (permalink / raw)
To: Krzysztof Adamski; +Cc: xfs
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?
-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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: NFS export broke with change from ext3 to xfs
2010-01-05 17:09 ` Eric Sandeen
@ 2010-01-05 17:21 ` Krzysztof Adamski
0 siblings, 0 replies; 6+ messages in thread
From: Krzysztof Adamski @ 2010-01-05 17:21 UTC (permalink / raw)
To: Eric Sandeen; +Cc: xfs
> 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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: NFS export broke with change from ext3 to xfs
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:43 ` Christoph Hellwig
2010-01-05 20:37 ` Emmanuel Florac
1 sibling, 1 reply; 6+ messages in thread
From: Christoph Hellwig @ 2010-01-05 17:43 UTC (permalink / raw)
To: Krzysztof Adamski; +Cc: xfs
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.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: NFS export broke with change from ext3 to xfs
2010-01-05 17:43 ` Christoph Hellwig
@ 2010-01-05 20:37 ` Emmanuel Florac
2010-01-06 18:09 ` Christoph Hellwig
0 siblings, 1 reply; 6+ messages in thread
From: Emmanuel Florac @ 2010-01-05 20:37 UTC (permalink / raw)
To: xfs
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: NFS export broke with change from ext3 to xfs
2010-01-05 20:37 ` Emmanuel Florac
@ 2010-01-06 18:09 ` Christoph Hellwig
0 siblings, 0 replies; 6+ messages in thread
From: Christoph Hellwig @ 2010-01-06 18:09 UTC (permalink / raw)
To: Emmanuel Florac; +Cc: xfs
On Tue, Jan 05, 2010 at 09:37:14PM +0100, Emmanuel Florac wrote:
> 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?
Unfortunately not. But if you specify a uuid in the /etc/exports
file it should use a different filesystem handle format that has space
for 8 byte inode numbers. I'm not entirely sure how nfsutils selects
them - it's been a while since I dealt with that code.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2010-01-06 18:08 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2010-01-06 18:09 ` Christoph Hellwig
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox