All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: lvm-devel@redhat.com
Subject: [QUESTION] lvmcache_label_scan: checksum error at offset xxx
Date: Thu, 10 Jun 2021 13:44:15 -0500	[thread overview]
Message-ID: <20210610184415.GA617@redhat.com> (raw)
In-Reply-To: <897da3d9-6818-05c0-7d77-ec35f7a635b7@huawei.com>

On Thu, Jun 10, 2021 at 05:19:17PM +0800, Wu Guanghao wrote:

> lvm[708341]: /dev/ram0: Checksum error at offset 203776
> lvm[708341]: WARNING: invalid metadata text from /dev/ram0 at 203776.
> lvm[708341]: WARNING: metadata on /dev/ram0 at 203776 has invalid summary for VG.
> lvm[708341]: WARNING: bad metadata text on /dev/ram0 in mda1
> lvm[708341]: WARNING: scanning /dev/ram0 mda1 failed to read metadata summary.

> lvm[639523]: WARNING: Metadata location on /dev/ram0 at 464384 begins with invalid VG name.
> lvm[639523]: WARNING: bad metadata text on /dev/ram0 in mda1
> lvm[639523]: WARNING: scanning /dev/ram0 mda1 failed to read metadata summary.

Hi, I'm not sure if these specific errors would be caused by the lock-less
label scan.  I would expect lvm to read valid but old metadata (which it
expects to find on occasion because of the lock-less scan.)  The full
command debugging along with a dd of the ondisk metadata areas would be
most helpful.

Thanks,
Dave



  parent reply	other threads:[~2021-06-10 18:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09  9:32 [QUESTION] lvmcache_label_scan: checksum error at offset xxx Wu Guanghao
2021-06-09 11:09 ` Zdenek Kabelac
2021-06-10  9:19   ` Wu Guanghao
2021-06-10  9:53     ` Zdenek Kabelac
2021-06-10 18:44     ` David Teigland [this message]
2021-06-11  1:53       ` Wu Guanghao
2021-06-11 21:50         ` David Teigland

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=20210610184415.GA617@redhat.com \
    --to=teigland@redhat.com \
    --cc=lvm-devel@redhat.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.