From: "Thomas Langås" <tlan@stud.ntnu.no>
To: jason andrade <jason@dstc.edu.au>
Cc: nfs@lists.sourceforge.net
Subject: Re: e1000 intel driver bug (which impacts nfs)
Date: Mon, 3 Jun 2002 00:28:19 +0200 [thread overview]
Message-ID: <20020603002819.A5501@stud.ntnu.no> (raw)
In-Reply-To: <Pine.OSF.4.20.0205262256430.16951-100000@azure.dstc.edu.au>; from jason@dstc.edu.au on Sun, May 26, 2002 at 11:06:06PM +1000
jason andrade:
> I hope this helps anyone else trying to debug mysterious "nfs hangs" under
> 2.4.X. It doesn't seem to be tickled unless you are doing quite large
> amounts of nfs traffic (we're pushing 1-1.5T a day on this interface)
> and it's quite random (i've had a lockup from 4 hours to 10 days after
> a reboot)
We've also got problems with nfs-hangs when transfering large files (ie.
files around 300-400M, sometime we have to go a bit higher tho, like
2GB-3GB files, but it's always possible to trigger this. However, we
don't need to be jumping through hoops to "fix it", after a min or so,
it's ok again. It seems to me like there's a VM problem or something.
We've got 2GB mem on the machines which are suffering from theese
problems.
--
Thomas
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-06-02 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-26 13:06 e1000 intel driver bug (which impacts nfs) jason andrade
2002-06-02 22:28 ` Thomas Langås [this message]
2002-06-03 2:30 ` seth vidal
2002-06-03 7:48 ` Trond Myklebust
2002-06-03 8:36 ` Ryan Sweet
-- strict thread matches above, loose matches on Subject: below --
2002-06-03 8:54 Mark Manuel Cruz Ramos
2002-06-05 15:04 darren.miller
2002-09-22 20:54 Allen Day
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=20020603002819.A5501@stud.ntnu.no \
--to=tlan@stud.ntnu.no \
--cc=jason@dstc.edu.au \
--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.