From: Kumar Gala <galak@kernel.crashing.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
nfs@lists.sourceforge.net, neilb@suse.de, bfields@fieldses.org,
chuck.lever@oracle.com
Subject: Re: LTP ustat01 test fails on NFSROOT
Date: Wed, 24 Oct 2007 00:05:32 -0500 [thread overview]
Message-ID: <1954B8FA-6E29-4FB7-86B0-EA43AF8F2AAF@kernel.crashing.org> (raw)
In-Reply-To: <1193188894.27073.20.camel@heimdal.trondhjem.org>
On Oct 23, 2007, at 8:21 PM, Trond Myklebust wrote:
>
> On Tue, 2007-10-23 at 17:52 -0500, Kumar Gala wrote:
>> I'm looking into an issue with LTP's ustat01 & ustat02 tests in which
>> they report the following:
>>
>> ustat01 1 FAIL : ustat(2) failed and setthe errno to 116 :
>> Stale NFS file handle
>> ustat02 2 FAIL : ustat(2) failed to produce expected error;
>> 14, errno: EFAULT and got 116
>>
>> It appears sometime between 2.6.21 and 2.6.22-rc1 some changes to NFS
>> got introduced that cause this.
>>
>> was wondering about any ideas while I try to debug what's going on.
>>
>> thanks
>>
>> - k
>
> I'm seeing zero problems with the latest checkouts from Linus' git
> tree.
> Mind giving us some more details?
I tried 2.6.24-rc1 w/the same result.
The system is a 32-bit PPC embedded board that we mounting the rootfs
over nfs on.
The defconfig is arch/powerpc/configs/mpc8641_hpcn_defconfig
> 'strace' output would be useful, as would the standard NFS list of
> client mount options, server export options, details on how your
> exported partition is set up on the server, etc...
strace:
stat64("/", {st_dev=makedev(0, 14), st_ino=58821800, st_mode=S_IFDIR|
0775, st_nlink=18, st_uid=500, st_gid=500, st_blksize=4096,
st_blocks=8, st_size=4096, st_atime=2007/10/23-22:43:30,
st_mtime=2007/10/18-19:51:19, st_ctime=2007/10/18-19:51:19}) = 0
ustat(0xe, 0x1001a008) = -1 ESTALE (Stale NFS file
handle)
fstat64(1, {st_dev=makedev(0, 14), st_ino=58821964, st_mode=S_IFCHR|
0600, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0,
st_rdev=makedev(4, 64), st_atime=2007/10/16-18:32:59,
st_mtime=2007/10/16-18:32:59, st_ctime=2007/10/24-05:03:34}) = 0
Info on the server:
[root@ducky ~]# exportfs -v
/ <world>(rw,async,wdelay,no_root_squash,no_subtree_check)
[root@ducky ~]# uname -a
Linux ducky.am.freescale.net 2.6.22.5-76.fc7 #1 SMP Thu Aug 30
13:04:34 EDT 2007 ppc64 ppc64 ppc64 GNU/Linux
On the host system:
(not sure how to get client mount options, mount reports:
%root% on / type unknown (rw)
-sh-2.05b# cat /proc/cmdline
root=/dev/nfs rw nfsroot=192.168.1.15:/home/galak/ltib-joust-8572/
rootfs
ip=192.168.1.147:192.168.1.15:192.168.1.1:255.255.254.0:rocky:eth0:off c
onsole=ttyS0,115200
If there is some other info that would be useful please let me know.
next prev parent reply other threads:[~2007-10-24 5:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 22:52 Kumar Gala
2007-10-24 1:21 ` Trond Myklebust
2007-10-24 5:05 ` Kumar Gala [this message]
2007-10-25 15:59 ` Kumar Gala
2007-10-25 17:59 ` Trond Myklebust
2007-10-25 18:36 ` Kumar Gala
2007-10-25 18:39 ` Trond Myklebust
2007-10-25 19:05 ` Kumar Gala
2007-10-26 9:42 ` Kumar Gala
2007-10-29 14:41 ` Kumar Gala
2007-11-02 14:28 ` Kumar Gala
2007-11-08 7:36 ` Kumar Gala
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=1954B8FA-6E29-4FB7-86B0-EA43AF8F2AAF@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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
all inboxes | Powered by JetHome®