From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: LVM Checksum error when using persistent grants (#linux-next + stable/for-jens-3.8)
Date: Fri, 7 Dec 2012 11:08:00 +0100 [thread overview]
Message-ID: <50C1C000.5020803@citrix.com> (raw)
In-Reply-To: <20121206031455.GA4408@phenom.dumpdata.com>
On 06/12/12 04:14, Konrad Rzeszutek Wilk wrote:
> Hey Roger,
>
> I am seeing this weird behavior when using #linux-next + 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.
>
> Have you seen something like this?
>
> Note, the other LV disks are over iSCSI and are working fine.
Thanks for the report Konrad, I'm able to reproduce this:
root@debian:~# pvscan -d -v /dev/xvdb2
Wiping cache of LVM-capable devices
Wiping internal VG cache
Walking through all physical volumes
PV /dev/xvdb2 lvm2 [4.99 GiB]
Total: 1 [4.99 GiB] / in use: 0 [0 ] / in no VG: 1 [4.99 GiB]
root@debian:~# pvscan -d -v /dev/xvdb2
Wiping cache of LVM-capable devices
Wiping internal VG cache
Walking through all physical volumes
No matching physical volumes found
What I find strange is that this only happens when using partitions as
LVM PVs, if I use the full disk (/dev/xvdb) as a PV I'm not able to
reproduce it. I will investigate further.
next prev parent reply other threads:[~2012-12-07 10:08 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é [this message]
2012-12-07 14:22 ` Konrad Rzeszutek Wilk
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=50C1C000.5020803@citrix.com \
--to=roger.pau@citrix.com \
--cc=konrad.wilk@oracle.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.