From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS woes in 2.5.1-pre8
Date: 12 Dec 2001 22:02:01 +0100 [thread overview]
Message-ID: <shsofl49mpi.fsf@charged.uio.no> (raw)
In-Reply-To: <20011212164334.B16377@flint.arm.linux.org.uk>
In-Reply-To: <20011212164334.B16377@flint.arm.linux.org.uk>
>>>>> " " == Russell King <rmk@arm.linux.org.uk> writes:
> I'm not sure if this is expected or not, but I'm seeing odd
> behaviour with NFS on 2.5.1-pre8:
> [root@assabet bin]$vdir ../lib -rwxr-xr-x 1 51 51 29091 Dec 12
> 2001 libts-0.0.so.0.0.0 ../lib: Input/output error
<snip>
> Admittedly raistlin is running a rather old, obsolete NFS
> server, which has up until now worked faultlessly for around 2
> years: Universal NFS Server 2.2beta48
> Appologies, but I'm not sure how I got it into this state
> either - last thing I had done was to overwrite the files in
> ../lib and bin with new sets on the NFS server. The only
> directory that is suffering is ../lib. (there's bin and
> ../include as well, both of which would've had their files
> overwritten with later versions).
There are (as of yet) no changes to the NFS client in 2.5.x.
Do you have any idea which syscall the above EIO is coming from? From
your tcpdump, it didn't appear to be coming from the server, and the
file attributes are getting displayed...
Cheers,
Trond
next prev parent reply other threads:[~2001-12-12 21:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 16:43 NFS woes in 2.5.1-pre8 Russell King
2001-12-12 21:02 ` Trond Myklebust [this message]
2001-12-15 16:02 ` Russell King
2001-12-16 15:06 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2001-12-12 17:22 Tyler BIRD
[not found] <sc172fdb.089@mail-smtp.uvsc.edu>
2001-12-12 17:29 ` Russell King
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=shsofl49mpi.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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