From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Miles Bader <miles@gnu.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS errors in 2.6
Date: 10 Dec 2003 08:33:24 -0500 [thread overview]
Message-ID: <shsu148ajbv.fsf@guts.uio.no> (raw)
In-Reply-To: <buobrqhun6r.fsf@mcspd15.ucom.lsi.nec.co.jp>
>>>>> " " == Miles Bader <miles@lsi.nec.co.jp> writes:
> My home directory is NFS-mounted from a Solaris server like:
> mccfs10:/mccfs10-4/soft1 /home/soft1 nfs
> nfsvers=3,rsize=1024,wsize=1024,noatime,nodiratime 0 0
(BTW: noatime and nodirtime don't make sense in an NFS
environment. There is no way to notify the server not to update
attributes)
> Frame 22 (158 bytes on wire, 158 bytes captured) Ethernet II,
> Src: 00:01:30:e9:cb:00, Dst: 00:03:47:97:9b:18 Internet
> Protocol, Src Addr: mccfs10.ucom.lsi.nec.co.jp (10.30.120.156),
> Dst Addr: mcspd15.ucom.lsi.nec.co.jp (10.30.114.174) User
> Datagram Protocol, Src Port: 2049 (2049), Dst Port: 800 (800)
> Remote Procedure Call, Type:Reply XID:0x0e72455c
> XID: 0xe72455c (242369884) Message Type: Reply (1) Program:
> NFS (100003) Program Version: 3 Procedure: READDIRPLUS (17)
> Reply State: accepted (0) This is a reply to a request in
> frame 21 Time from request: 0.001394000 seconds Verifier
> Flavor: AUTH_NULL (0) Length: 0
> Accept State: RPC executed successfully (0)
> Network File System, READDIRPLUS Reply Error:ERR_INVAL
> Program Version: 3 V3 Procedure: READDIRPLUS (17) Status:
> ERR_INVAL (22) dir_attributes
Interesting. That actually looks like an error on the part of your
Solaris server. NFS3ERR_INVAL is not a valid return code for either
READDIR or for READDIRPLUS according to RFC1813.
Is the server being kept up to scratch on the patch side?
Cheers,
Trond
next prev parent reply other threads:[~2003-12-10 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 7:49 NFS errors in 2.6 Miles Bader
2003-12-10 13:33 ` Trond Myklebust [this message]
2003-12-11 2:19 ` Miles Bader
2003-12-11 2:39 ` Trond Myklebust
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=shsu148ajbv.fsf@guts.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@gnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.