Hi: I have a 4TB XFS filesystem mounted with "inode64" option, and I exported it using NFS v3, on NFS client, I entered a subdirectory and got "stale NFS file handle" error. ls -il showed that its in
Le Mon, 21 Nov 2011 21:00:57 +0800 hank peng <pengxihan@xxxxxxxxx> écrivait: Are the client and the server running a 64 bits kernel? -- -- Emmanuel Florac | Direction technique <eflorac@xxxxxxxxxxxxx
no, client and server are both 32 bits kernel. 2011/11/21 Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>: -- The simplest is not all best but the best is surely the simplest!
Le Mon, 21 Nov 2011 23:02:32 +0800 hank peng <pengxihan@xxxxxxxxx> écrivait: I'm afraid the 32 bits nfs client can't manage 64 bits inodes at all. Maybe with a much more recent kernel, something like
2011/11/21 Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>: I noticed that there is a kernel parameter : nfs.enable_ino64= [NFS] enable 64-bit inode numbers. If zero, the NFS client will fake up a 32-bit in
Le Mon, 21 Nov 2011 23:28:23 +0800 hank peng <pengxihan@xxxxxxxxx> écrivait: Well you must try it and hope for the best! -- -- Emmanuel Florac | Direction technique <eflorac@xxxxxxxxxxxxxx> --
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 t
2011/11/22 Christoph Hellwig <hch@xxxxxxxxxxxxx>: 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 in
^^^^^^^^^^^^^^ no_root_squash It's in the FAQ entry christoph pointed you to: "However, exporting the root of the filesystem works" Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx
2011/11/22 Dave Chinner <david@xxxxxxxxxxxxx>: sorry, it is my type mistake, it is no_root_squash. I think I have already exported the root of my XFS filesystem, am I right? -- The simplest is not al
unfortunately, seting nfs.enable_ino64 didn't work although it gave me 32 bit inode number indeed, I think there must be something else wrong. 2011/11/21 Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>: --
Le Tue, 22 Nov 2011 11:22:15 +0800 vous écriviez: Yes, and the fsid stuff only relates to NFS v4, and as you aren't providing any fsid, you must be running NFS 3. Now maybe you could use NFS 4 instea
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
2011/11/23 Christoph Hellwig <hch@xxxxxxxxxxxxx>: yes, I have already done that. I mount the expoted NFS directory in same machine(kernel version is 2.6.35.6), but it still didn't work. Then, I used
Ok, sounds like this is a server side issue. Do you mean the NFS mount displayed a 32-bit inode number, but it was still 64-bit on the XFS filesystem directly? Can you post the inode numbers (e.g. fr