From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Kumar Gala <galak@kernel.crashing.org>
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: Tue, 23 Oct 2007 21:21:34 -0400 [thread overview]
Message-ID: <1193188894.27073.20.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <CBDE987B-0713-4D62-8122-054183E75410@kernel.crashing.org>
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?
'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...
Trond
next prev parent reply other threads:[~2007-10-24 1:20 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 [this message]
2007-10-24 5:05 ` Kumar Gala
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=1193188894.27073.20.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
/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®