linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: "Kojedzinszky Richárd" <kojedzinszky.richard@euronetrt.hu>,
	Xen-devel <xen-devel@lists.xenproject.org>
Cc: linux-nfs@vger.kernel.org, wei.liu2@citrix.com,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Subject: blk_update_request: I/O error on NFS  (was: [Xen-users] xen domU disk on nfs shared file)
Date: Tue, 12 Jan 2016 12:05:48 +0000	[thread overview]
Message-ID: <20160112120548.GB27051@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1601111458420.24727@krichy.tvnetwork.hu>

Drop xen-users@, CC xen-devel@ and blk maintainers, change title.

On Mon, Jan 11, 2016 at 03:08:24PM +0100, Kojedzinszky Richárd 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 files 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=3,rsize=16384,wsize=16384,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.1.1.1,mountvers=3,mountport=4045,mountproto=udp,local_lock=none,addr=10.1.1.1)
> 
> After starting the instance I partitioned the disk with gdisk, and created
> 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 (probably
> 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árd
> Euronet Magyarorszag Informatika Zrt.

> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users


  reply	other threads:[~2016-01-12 12:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11 14:08 xen domU disk on nfs shared file Kojedzinszky Richárd
2016-01-12 12:05 ` Wei Liu [this message]
2016-01-12 12:58   ` blk_update_request: I/O error on NFS Roger Pau Monné

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=20160112120548.GB27051@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=kojedzinszky.richard@euronetrt.hu \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).