From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: blk_update_request: I/O error on NFS (was: [Xen-users] xen domU disk on nfs shared file) Date: Wed, 27 Jan 2016 12:40:17 -0500 Message-ID: <20160127174017.GE2258@char.us.oracle.com> References: <20160112120548.GB27051@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aOU55-0003LD-43 for xen-devel@lists.xenproject.org; Wed, 27 Jan 2016 17:40:35 +0000 Content-Disposition: inline In-Reply-To: <20160112120548.GB27051@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Wei Liu Cc: Xen-devel , Kojedzinszky =?iso-8859-1?Q?Rich=E1rd?= , linux-nfs@vger.kernel.org, Roger Pau =?iso-8859-1?Q?Monn=E9?= List-Id: xen-devel@lists.xenproject.org On Tue, Jan 12, 2016 at 12:05:48PM +0000, Wei Liu wrote: > Drop xen-users@, CC xen-devel@ and blk maintainers, change title. > = What is the MTU you are using? How do you mount the disk? > On Mon, Jan 11, 2016 at 03:08:24PM +0100, Kojedzinszky Rich=E1rd wrote: > > Dear all, > > = > > We are facing a regular lockup with our xen setup. We have an nfs share > > mounted on the xen dom0, where the vm images are served, and those file= s are > > given to xen domUs. > > = > > I was just preparing an experiment, where I created a 100G file on the = host: > > # truncate -s 100G /srv/nfs/domU/disk2 > > And after added this disk to the instance's configuration. > > = > > On the host this is the mountpoint: > > # mount|grep srv/xen > > 10.1.1.1:/mnt/main/vps on /srv/xen type nfs (rw,relatime,vers=3D3,rsize= =3D16384,wsize=3D16384,namlen=3D255,hard,proto=3Dtcp,timeo=3D600,retrans=3D= 2,sec=3Dsys,mountaddr=3D10.1.1.1,mountvers=3D3,mountport=3D4045,mountproto= =3Dudp,local_lock=3Dnone,addr=3D10.1.1.1) > > = > > After starting the instance I partitioned the disk with gdisk, and crea= ted > > an xfs fs on it. While the fs has been created well, strange messages > > appeared on the console: > > = > > [ 23.787504] blk_update_request: I/O error, dev xvdc, sector 2048 > > [ 23.788904] blk_update_request: I/O error, dev xvdc, sector 8390655 > > [ 23.789611] blk_update_request: I/O error, dev xvdc, sector 16779262 > > [ 23.790359] blk_update_request: I/O error, dev xvdc, sector 25167869 > > [ 23.791148] blk_update_request: I/O error, dev xvdc, sector 33556476 > > [ 23.791498] blk_update_request: I/O error, dev xvdc, sector 41945083 > > [ 23.791498] blk_update_request: I/O error, dev xvdc, sector 50333690 > > [ 23.791498] blk_update_request: I/O error, dev xvdc, sector 58722297 > > [ 23.791498] blk_update_request: I/O error, dev xvdc, sector 67110904 > > [ 23.791498] blk_update_request: I/O error, dev xvdc, sector 75499511 > > = > > I dont think that this is normal. If I chose a local block device (prob= ably > > lvm) for the domU, this does not appear. > > = > > The host is running xen-4.4 with 3.16.0-4-amd64 kernel (debian jessie > > stock), the domU is running 4.3.0-0.bpo.1-amd64 (jessie backport, 4.4.4= ). > > = > > I suspect those messages should not be there. > > = > > Regards, > > = > > Kojedzinszky Rich=E1rd > > Euronet Magyarorszag Informatika Zrt. > = > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xen.org > > http://lists.xen.org/xen-users > =