From: Kip Macy <kip.macy@gmail.com>
To: Chris Wright <chrisw@osdl.org>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: copying large files over NFS locks up machine on -testing from Thursday
Date: Sat, 21 May 2005 13:32:29 -0700 [thread overview]
Message-ID: <b1fa2917050521133231869094@mail.gmail.com> (raw)
In-Reply-To: <20050521183920.GJ19113@shell0.pdx.osdl.net>
If it happens on -unstable in domUs (it probably does) I can grab a
coredump or attach to it while it is running and see where it is
wedged. I don't have a port master where I'm at so I can't use pdb or
cdb.
-Kip
On 5/21/05, Chris Wright <chrisw@osdl.org> wrote:
> * Kip Macy (kip.macy@gmail.com) wrote:
> > 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
>
> Hmm, I've seen this on stock 2.6.11 kernels as well (no xen). Any chance
> you can get useful debugging out it?
>
> thanks,
> -chris
>
next prev parent reply other threads:[~2005-05-21 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-21 18:06 copying large files over NFS locks up machine on -testing from Thursday Kip Macy
2005-05-21 18:25 ` Robert Read
2005-05-21 18:39 ` Chris Wright
2005-05-21 20:32 ` Kip Macy [this message]
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=b1fa2917050521133231869094@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=chrisw@osdl.org \
--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.