linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
	Krzysztof Chojnowski <frirajder@gmail.com>
Subject: Re: [linux-lvm] LVM cachepool inconsistency after power event
Date: Tue, 5 Oct 2021 17:51:23 +0200	[thread overview]
Message-ID: <b9e10482-e508-63fa-5518-94cccc007e81@redhat.com> (raw)
In-Reply-To: <CAPWGHt3bB4QiM6RZkC_58X8jev+mVwpkuCY==45Gr4j5jOYHBA@mail.gmail.com>

Dne 05. 10. 21 v 13:34 Krzysztof Chojnowski napsal(a):
> On Tue, Oct 5, 2021 at 06:35 AM Ming-Hung Tsai <mingnus@gmail.com> wrote:
>> Could you help run cache_check independently, to see the error messages? Thanks.
>>
>> # sudo lvchange -ay -f vg0/wdata_cachepool_cpool_cmeta
>> # sudo cache_check /dev/mapper/vg0-wdata_cachepool_cpool_cmeta
>> # sudo lvchange -an -f vg0/wdata_cachepool_cpool_cmeta
> 
> Thanks for your help, this is what I get:
> $ sudo lvchange -ay -f vg0/wdata_cachepool_cpool_cmeta
> Do you want to activate component LV in read-only mode? [y/n]: y
>    Allowing activation of component LV.
> $ sudo cache_check /dev/mapper/vg0-wdata_cachepool_cpool_cmeta
> examining superblock
> examining mapping array
>    missing mappings [1, 0]:
>      missing blocks
> examining hint array
>    missing mappings [1, 0]:
>      missing blocks
> examining discard bitset
> $ echo $?
> 1
> $ sudo lvchange -an -f vg0/wdata_cachepool_cpool_cmeta
> $ sudo lvchange -ay   vg0/tpg1-wdata
>    Check of pool vg0/wdata_cachepool_cpool failed (status:1). Manual
> repair required!

Hello Krzystof

You need to repair your cache-pool metadata.

But before continuing with advices - what is the version of kernel lvm2 & your
device-mapper-persistent-data package (aka  'cache_check -V)

Component activation allows activation of your _cmeta LV - but only in 
read-only mode - so repair must go into a new LV.

Since cache_check reported  '1' exist code (as an error) - your metadata do 
require a fix.

lvconvert --repair should be able to handle this case - although likely 
without 'smart' placement' of fixed metadata (pvmove needed after metadata fix)

You can allocated your new metadata and easily cache_repair them.


Regards

Zdenek

_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/


  reply	other threads:[~2021-10-05 15:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04 13:30 Krzysztof Chojnowski
2021-10-05 10:34 ` Ming-Hung Tsai
2021-10-05 11:34 ` Krzysztof Chojnowski
2021-10-05 15:51   ` Zdenek Kabelac [this message]
2021-10-05 16:56     ` Ming Hung Tsai
2021-10-06  8:27       ` Krzysztof Chojnowski
2021-10-08  7:56         ` Ming Hung Tsai
2021-10-11 12:16           ` Krzysztof Chojnowski
2021-10-11 16:29             ` Ming Hung Tsai
2021-10-11 18:57               ` Krzysztof Chojnowski
2021-10-05 11:13 Krzysztof Chojnowski

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=b9e10482-e508-63fa-5518-94cccc007e81@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=frirajder@gmail.com \
    --cc=linux-lvm@redhat.com \
    --subject='Re: [linux-lvm] LVM cachepool inconsistency after power event' \
    /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

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).