All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com, Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: LVM Checksum error when using persistent grants (#linux-next + stable/for-jens-3.8)
Date: Fri, 7 Dec 2012 09:22:23 -0500	[thread overview]
Message-ID: <20121207142222.GA3303@phenom.dumpdata.com> (raw)
In-Reply-To: <20121206031455.GA4408@phenom.dumpdata.com>

On Wed, Dec 05, 2012 at 10:14:55PM -0500, Konrad Rzeszutek Wilk wrote:
> Hey Roger,
> 
> I am seeing this weird behavior when using #linux-next + stable/for-jens-3.8 tree.

To make it easier I just used v3.7-rc8 and merged stable/for-jens-3.8
tree.

> 
> Basically I can do 'pvscan' on xvd* disk and quite often I get checksum errors:
> 
> # pvscan /dev/xvdf
>   PV /dev/xvdf2   VG VolGroup00        lvm2 [18.88 GiB / 0    free]
>   PV /dev/dm-14   VG vg_x86_64-pvhvm   lvm2 [4.00 GiB / 68.00 MiB free]
>   PV /dev/dm-12   VG vg_i386-pvhvm     lvm2 [4.00 GiB / 68.00 MiB free]
>   PV /dev/dm-11   VG vg_i386           lvm2 [4.00 GiB / 68.00 MiB free]
>   PV /dev/sda     VG guests            lvm2 [931.51 GiB / 220.51 GiB free]
>   Total: 5 [962.38 GiB] / in use: 5 [962.38 GiB] / in no VG: 0 [0   ]
> # pvscan /dev/xvdf
>   /dev/xvdf2: Checksum error
>   Couldn't read volume group metadata.
>   /dev/xvdf2: Checksum error
>   Couldn't read volume group metadata.
>   PV /dev/dm-14   VG vg_x86_64-pvhvm   lvm2 [4.00 GiB / 68.00 MiB free]
>   PV /dev/dm-12   VG vg_i386-pvhvm     lvm2 [4.00 GiB / 68.00 MiB free]
>   PV /dev/dm-11   VG vg_i386           lvm2 [4.00 GiB / 68.00 MiB free]
>   PV /dev/sda     VG guests            lvm2 [931.51 GiB / 220.51 GiB free]
>   Total: 4 [943.50 GiB] / in use: 4 [943.50 GiB] / in no VG: 0 [0   ]
> 
> This is with a i386 dom0, 64-bit Xen 4.1.3 hypervisor, and with either
> 64-bit or 32-bit PV or PVHVM guest.

And it does not matter if dom0 is 64-bit.
> 
> Have you seen something like this?

More interestingly is that the failure is the frontend. I ran the "new"
guests that do persistent grants with the old backends (so v3.7-rc8
virgin) and still got the same failure.

> 
> Note, the other LV disks are over iSCSI and are working fine.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
> 

  parent reply	other threads:[~2012-12-07 14:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24 16:58 [PATCH v2] Persistent grant maps for xen blk drivers Roger Pau Monne
2012-10-29 13:57 ` Konrad Rzeszutek Wilk
2012-10-29 13:57 ` Konrad Rzeszutek Wilk
2012-10-30 17:01 ` Konrad Rzeszutek Wilk
2012-10-30 17:01 ` Konrad Rzeszutek Wilk
2012-10-30 18:33   ` Roger Pau Monné
2012-10-30 18:33   ` Roger Pau Monné
2012-10-30 20:38     ` Konrad Rzeszutek Wilk
2012-10-30 20:38     ` Konrad Rzeszutek Wilk
2012-12-06  3:14 ` LVM Checksum error when using persistent grants (#linux-next + stable/for-jens-3.8) Konrad Rzeszutek Wilk
2012-12-07 10:08   ` Roger Pau Monné
2012-12-07 14:22   ` Konrad Rzeszutek Wilk [this message]
2012-12-07 17:05     ` 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=20121207142222.GA3303@phenom.dumpdata.com \
    --to=konrad@kernel.org \
    --cc=konrad.wilk@oracle.com \
    --cc=roger.pau@citrix.com \
    --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.