From: "H . J . Lu" <hjl@lucon.org>
To: "Cooke, Alan" <acooke@hp.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: RedHat 7.3 crashed NetApp?
Date: Fri, 17 May 2002 08:11:25 -0700 [thread overview]
Message-ID: <20020517081125.A5553@lucon.org> (raw)
In-Reply-To: <C0B72BFE4E6CFF4C97FDB17BED66E84A085DB7@cceexc15.americas.cpqcorp.net>; from acooke@hp.com on Fri, May 17, 2002 at 08:14:37AM -0500
On Fri, May 17, 2002 at 08:14:37AM -0500, Cooke, Alan wrote:
> While running the 2.4.18-4smp kernel (RedHat), and testing NFS3, our NetApp filer running OnTap 6.1.1R2 experienced massive incoming traffic from the Linux client in question. The Linux client required rebooting. We have been able to repeat this behavior, and are suspicious of the network driver on the Linux client which is using the eth0 driver. A
>
I think it is the same as what happened to me. I had to reboot/unplug
my Linux client before the whole NFS network went down. I am using Intel
e100 driver on eepro100. But my Linux NFS severs have no problem with
that client.
H.J.
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-05-17 15:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-17 13:14 RedHat 7.3 crashed NetApp? Cooke, Alan
2002-05-17 15:11 ` H . J . Lu [this message]
2002-05-17 17:16 ` Daryl Herzmann
2002-05-17 17:32 ` Benjamin LaHaise
-- strict thread matches above, loose matches on Subject: below --
2002-05-21 21:53 Vladimir Vuksan
2002-05-20 14:19 Lever, Charles
2002-05-20 14:46 ` Benjamin LaHaise
2002-05-17 22:17 Lever, Charles
2002-05-18 0:17 ` Benjamin LaHaise
2002-05-18 1:43 ` seth vidal
2002-05-16 22:39 H . J . Lu
2002-05-16 23:16 ` seth vidal
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=20020517081125.A5553@lucon.org \
--to=hjl@lucon.org \
--cc=acooke@hp.com \
--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 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.