From: Athanasius <Athan@gurus.tf>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Burj?n G?bor <buga+dated+1013036430.1fd862@elte.hu>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: 2.4.17 NFS hangup
Date: Mon, 4 Feb 2002 14:47:20 +0000 [thread overview]
Message-ID: <20020204144720.GD18430@gurus.tf> (raw)
In-Reply-To: <20020203202251.GA22797@csoma.elte.hu> <shsbsf61di3.fsf@charged.uio.no> <20020203213422.GA703@csoma.elte.hu> <15453.48475.123973.610574@charged.uio.no> <20020203230030.GA14478@csoma.elte.hu> <20020204132146.GB18430@gurus.tf>
In-Reply-To: <20020204132146.GB18430@gurus.tf>
[-- Attachment #1: Type: text/plain, Size: 1427 bytes --]
On Mon, Feb 04, 2002 at 01:21:46PM +0000, Athanasius wrote:
> I'm seeing something like this as well. Two machines using
> BNC/thinwire (yes, I know, waiting on finances to make this better), 2
> other machines on the same segment. I use an NFS mount from the server
> (jimblewix) on the workstation (emelia) for amongst other things playing
> mp3s.
Seems to be my day for this happening. A bit more data:
There's next to no collisions going on, from ifconfig eth0 on the
SERVER:
RX packets:31331103 errors:0 dropped:1 overruns:0 frame:151
TX packets:42576602 errors:0 dropped:0 overruns:0 carrier:0
collisions:33733 txqueuelen:100
and the WORKSTATION:
RX packets:301884 errors:0 dropped:0 overruns:0 frame:0
TX packets:238086 errors:0 dropped:0 overruns:0 carrier:0
collisions:397 txqueuelen:100
Also the numbers on the SERVER at least for collisions didn't increase
the last time NFS cut out on me.
I'm not seeing ANY other logging in kern.log on either machine above
the NFS timeout reports, nothing about NICs having trouble or the like.
-Ath
--
- Athanasius = Athanasius(at)gurus.tf / http://www.clan-lovely.org/~athan/
Finger athan(at)fysh.org for PGP key
"And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence." Paula Cole - ME
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
prev parent reply other threads:[~2002-02-04 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-03 20:22 2.4.17 NFS hangup Burjan Gabor
2002-02-03 21:06 ` Trond Myklebust
2002-02-03 21:34 ` Burján Gábor
2002-02-03 21:58 ` Alan Cox
2002-02-03 22:44 ` Trond Myklebust
2002-02-03 23:00 ` Burján Gábor
2002-02-04 13:21 ` Athanasius
2002-02-04 14:47 ` Athanasius [this message]
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=20020204144720.GD18430@gurus.tf \
--to=athan@gurus.tf \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=buga+dated+1013036430.1fd862@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--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