From: Kip Macy <kip.macy@gmail.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: copying large files over NFS locks up machine on -testing from Thursday
Date: Sat, 21 May 2005 11:06:57 -0700 [thread overview]
Message-ID: <b1fa2917050521110624e36e58@mail.gmail.com> (raw)
I've locked up my dom0 a couple of times this morning copying a 3GB
file from local disk to an NFS mount(neither xend nor guests running).
I don't encounter this problem on the stock CentOS 4 kernel. The
machine is a PowerEdge 2850 with 2 e1000 cards - the one in use is
connected to a PowerConnect 2216 10/100 switch and has negotiated
100Mbit. I'll check if the stock Cambridge isn't negotiating full
duplex but that shouldn't cause lockups.
My mount options are:
defaults,intr,rsize=32768,wsize=32768,nfsvers=3,tcp,timeo=600
This isn't at NetApp (no 100Mbit there), but these are the options
used by all their linux NFS clients.
next reply other threads:[~2005-05-21 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-21 18:06 Kip Macy [this message]
2005-05-21 18:25 ` copying large files over NFS locks up machine on -testing from Thursday Robert Read
2005-05-21 18:39 ` Chris Wright
2005-05-21 20:32 ` Kip Macy
2005-05-21 21:41 ` Kip Macy
2005-05-21 23:40 ` Kip Macy
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=b1fa2917050521110624e36e58@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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.