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: Sat, 21 May 2005 14:41:48 -0700 Message-ID: References: <20050521183920.GJ19113@shell0.pdx.osdl.net> 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: <20050521183920.GJ19113@shell0.pdx.osdl.net> 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: Chris Wright Cc: xen-devel List-Id: xen-devel@lists.xenproject.org I just tried copying the 3GB file over NFS from within a domU on -testing in hopes of getting some debug info. dom0 became unresponsive for a few seconds after close to a minute. It had successfully copied 2.3GB when I hit ^C and then started a copy from NFS to the domU's / which itself is a loopback device mounted over NFS in dom0 - shortly thereafter the machine locked up, the only output being complaints from megaraid about aborted SCSI commands. It seems possible that this is a dom0 issue. I'll try building a stock linux 2.6.11.10 kernel with the same non-xen options as the Cambridge kernel to see if it has the same issues. After that I'll just stick to having everything on local disk until I get moved to a GigE network at which point I can start testing migration. -Kip On 5/21/05, Chris Wright 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=3D32768,wsize=3D32768,nfsvers=3D3,tcp,timeo=3D600 >=20 > Hmm, I've seen this on stock 2.6.11 kernels as well (no xen). Any chance > you can get useful debugging out it? >=20 > thanks, > -chris >