From: "Tyler BIRD" <BIRDTY@uvsc.edu>
To: <rmk@arm.linux.org.uk>, <linux-kernel@vger.kernel.org>
Subject: Re: NFS woes in 2.5.1-pre8
Date: Wed, 12 Dec 2001 10:22:04 -0700 [thread overview]
Message-ID: <sc172fdb.090@mail-smtp.uvsc.edu> (raw)
Search the kernel sources at: http://lxr.linux.no/source/kernel/?v=2.4.13 or 2.4.26, etc
I know the ip addres for each interface are stored somewhere.
They have to be because they are passed down to the net driver inside of socket buffers ( skb )
as a struct tcphdr * and they have to be appended to each packet.
Tyler
>>> Russell King <rmk@arm.linux.org.uk> 12/12/01 09:43AM >>>
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
[root@assabet bin]$uname -a
Linux assabet 2.5.1-pre8 #69 Mon Dec 10 22:21:15 GMT 2001 armv4l unknown
[root@assabet bin]$
Looking at the NFS traffic:
16:27:09.051301 assabet.arm.linux.org.uk.33f11c24 > raistlin.arm.linux.org.uk.nfs: 148 lookup fh Unknown/1 "libts-0.0.so.0" (DF)
16:27:09.061306 raistlin.arm.linux.org.uk.nfs > assabet.arm.linux.org.uk.33f11c24: reply ok 128 lookup fh Unknown/1 (DF)
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).
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-12-12 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 17:22 Tyler BIRD [this message]
[not found] <sc172fdb.089@mail-smtp.uvsc.edu>
2001-12-12 17:29 ` NFS woes in 2.5.1-pre8 Russell King
-- strict thread matches above, loose matches on Subject: below --
2001-12-12 16:43 Russell King
2001-12-12 21:02 ` Trond Myklebust
2001-12-15 16:02 ` Russell King
2001-12-16 15:06 ` 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=sc172fdb.090@mail-smtp.uvsc.edu \
--to=birdty@uvsc.edu \
--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