From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kip Macy Subject: Re: copying large files over NFS locks up machine on-testing from Thursday Date: Sun, 22 May 2005 11:42:36 -0700 Message-ID: References: Reply-To: Kip Macy Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Pratt Cc: Chris Wright , xen-devel List-Id: xen-devel@lists.xenproject.org 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 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. >=20 > I'll just skip migration testing for now. >=20 > -Kip >=20 >=20 >=20 > On 5/21/05, Kip Macy wrote: > > > It sounds like the megaraid driver is unhappy. Can you reproduce thi= s > > > 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 > > >