All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kip Macy <kip.macy@gmail.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Chris Wright <chrisw@osdl.org>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: Re: copying large files over NFS locks up machine on-testing from Thursday
Date: Sun, 22 May 2005 11:42:36 -0700	[thread overview]
Message-ID: <b1fa291705052211426ce50fff@mail.gmail.com> (raw)
In-Reply-To: <b1fa2917050522112474188305@mail.gmail.com>

No bridge helps with NFS, but I just tried scp on a freshly re-booted
machine and it locked up instantly. Booting into Centos4 SMP and the
scp works fine - if this a SUE it is a particularly inventive one.

I guess it is time to move to the server room and cross my fingers
that this is a 100Mbit issue.

         -Kip


On 5/22/05, Kip Macy <kip.macy@gmail.com> wrote:
> I just updated to 2.0.6. Large NFS transfers work fine with the
> default configuration. If xend has been started (i.e. the bridge has
> been configured) the machine will become unresponsive when copying a
> large file over NFS.
> 
> I'll just skip migration testing for now.
> 
>         -Kip
> 
> 
> 
> On 5/21/05, Kip Macy <kip.macy@gmail.com> wrote:
> >  > It sounds like the megaraid driver is unhappy. Can you reproduce this
> > > copying the file to /dev/null?
> >
> > I think it was unhappy because its interrupts weren't being serviced.
> > Copying /home/kmacy/suseroot.0 to /home/kmacy/suseroot.1 (NFS -> NFS)
> > locks the machine up just fine. The machine will also become
> > unresponsive transiently when running fsck in domU on a filesystem
> > that is a loopback device mounted over NFS.
> >
> > > It's worth checking the Dell site to make sure you have the latest
> > > megaraid firmware and driver.
> >
> > Running native mainline 2.6.11.10 NFS transfers don't cause any
> > problems. To reduce the possibility of it being a benchmark-like SUE
> > I'll do a clean build from scratch of the dom0 kernel.
> >
> >
> >         -Kip
> >
>

  reply	other threads:[~2005-05-22 18:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-22  2:51 copying large files over NFS locks up machine on-testing from Thursday Ian Pratt
2005-05-22  3:26 ` Kip Macy
2005-05-22 18:24   ` Kip Macy
2005-05-22 18:42     ` Kip Macy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-22 19:36 Ian Pratt
2005-05-22 19:54 ` Kip Macy
2005-05-22 20:40   ` Kip Macy
2005-05-22 18:40 Ian Pratt
2005-05-22 19:24 ` Kip Macy
2005-05-21 20:40 Ian Pratt

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=b1fa291705052211426ce50fff@mail.gmail.com \
    --to=kip.macy@gmail.com \
    --cc=chrisw@osdl.org \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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.