From: Ming Hung Tsai <mtsai@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM cachepool inconsistency after power event
Date: Fri, 8 Oct 2021 15:56:48 +0800 [thread overview]
Message-ID: <CALjSBEt0TdOr4jL4JhCKrRCfO+LiT_0tNaQYfQ9mLgQNjhq8Aw@mail.gmail.com> (raw)
In-Reply-To: <CAPWGHt11L-ZGtLbZ08UVga7WP5fq6pY7gUS9HYtnVWvB11zj7Q@mail.gmail.com>
On Thu, Oct 7, 2021 at 3:57 PM Krzysztof Chojnowski <frirajder@gmail.com> wrote:
>
> On Tue, Oct 5, 2021 at 6:57 PM Ming Hung Tsai <mtsai@redhat.com> wrote:
>>
>> On Tue, Oct 5, 2021 at 11:54 PM Zdenek Kabelac <zkabelac@redhat.com> wrote:
>>
>> > lvconvert --repair should be able to handle this case - although likely
>> > without 'smart' placement' of fixed metadata (pvmove needed after metadata fix)
>
> I tried running lvconvert --repair earlier (please see the 1st of my mails) and even trough the operation finished successfully (as in the $? == 0) I couldn't activate the volume afterwards.
>
>>
>> cache_repair might not handle this case perfectly. If possible, you
>> could upload the "original" metadata somewhere for me to take a look,
>> by dd it into a binary file.
>
> Unfortunately I deleted the original metadata volume when I was trying to remove the cached volume.
> So right now, I guess, the question is how do I remove the cached volume, as the repair doesn't seem to be possible.
Hi,
You could simply detach the cache:
sudo lvconvert vg0/tpg1-wdata --splitcache
Or alternatively, reinitialize the cache by swapping the metadata with
a blank one, which bypasses cache_check examination and then steps to
metadata formatting:
sudo lvcreate vg0 --size 40m --name cmeta_bak
sudo lvconvert vg0/wdata_cachepool_cpool --swapmetadata --poolmetadata cmeta_bak
then you should be able to activate the tpg1-wdata.
BTW, could you help provide the reproducing steps? I guess that you
performed a power cut soon after creating the cache. Thanks.
Ming-Hung Tsai
_______________________________________________
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/
next prev parent reply other threads:[~2021-10-08 7:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 13:30 [linux-lvm] LVM cachepool inconsistency after power event Krzysztof Chojnowski
2021-10-05 10:34 ` Ming-Hung Tsai
2021-10-05 11:34 ` Krzysztof Chojnowski
2021-10-05 15:51 ` Zdenek Kabelac
2021-10-05 16:56 ` Ming Hung Tsai
2021-10-06 8:27 ` Krzysztof Chojnowski
2021-10-08 7:56 ` Ming Hung Tsai [this message]
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=CALjSBEt0TdOr4jL4JhCKrRCfO+LiT_0tNaQYfQ9mLgQNjhq8Aw@mail.gmail.com \
--to=mtsai@redhat.com \
--cc=linux-lvm@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 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).