| To: | hank peng <pengxihan@xxxxxxxxx> |
|---|---|
| Subject: | Re: stale NFS file handle problem on XFS inode64 |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Mon, 28 Nov 2011 06:09:41 -0500 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <CAJNJY8Q3u6zZYHVdxnka160f+EC21JxoBe4EyKk=vDQgH4T19w@xxxxxxxxxxxxxx> |
| References: | <CAJNJY8Q--O2Z3K6KFxVKOivwaABk+oRtC1y0eQ0nS1WdPNMwsQ@xxxxxxxxxxxxxx> <20111121170459.GA1327@xxxxxxxxxxxxx> <CAJNJY8Ty+bQpzGL9wq7Qv3ozcKUPwmTyYUeb2wQqZ326K4JeWw@xxxxxxxxxxxxxx> <20111122221515.GA29540@xxxxxxxxxxxxx> <CAJNJY8Q3u6zZYHVdxnka160f+EC21JxoBe4EyKk=vDQgH4T19w@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Wed, Nov 23, 2011 at 09:19:26AM +0800, hank peng wrote: > 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. Ok, sounds like this is a server side issue. > > Then, I used fsid=$(my exported filesystem ID) option in /etc/exports > and tried again, it still gave me back "stale NFS file handle" when > entering a specific subdirectory. > I noticed that from NFS client(in same machine with NFS server) side, > the inode number of this subdirectory was changed to be within 32 > limit, but still "stale NFS file handle" came back. 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. from ls -i) for both sides? |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] xfstests: mount other filesystems with selinux context as well, Christoph Hellwig |
|---|---|
| Next by Date: | Re: xfs: validate inode numbers in file handles correctly, Christoph Hellwig |
| Previous by Thread: | Re: stale NFS file handle problem on XFS inode64, hank peng |
| Next by Thread: | CSO Conference & Award 06 - 07/12/2011 at Sheraton Hotel, HCMC, CSO Conf & Award 2011 |
| Indexes: | [Date] [Thread] [Top] [All Lists] |