From: Marian Csontos <mcsontos@redhat.com>
To: listac@nebelschwaden.de,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] metadata device too small
Date: Mon, 13 Jan 2020 16:02:06 +0100 [thread overview]
Message-ID: <bdbb0195-8b35-f732-1db8-641c3fbdc20f@redhat.com> (raw)
In-Reply-To: <28fac0e3-5853-76e2-5f9f-c4ae7b35c4a8@nebelschwaden.de>
On 1/11/20 11:07 PM, Ede Wolf wrote:
>>> Is there any way to make the data accessible again?
>>>
>>> lvm2 2.02.186
lvm2 version is not that important in this case, you will want to try a
newer thin-provisioning-tools package.
I see the newest version in Ubuntu is 0.7.6 while upstream is at 0.8.5
with some bugs in thin metadata repair fixed.
You can compile yourself, or could try using e.g. live Fedora 31 with up
to date package.
-- Marian
>>>
>>>
>>> _______________________________________________
>>> linux-lvm mailing list
>>> linux-lvm@redhat.com
>>> https://www.redhat.com/mailman/listinfo/linux-lvm
>>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>>>
>>
>>
>> _______________________________________________
>> linux-lvm mailing list
>> linux-lvm@redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-lvm
>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2020-01-13 15:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 17:57 [linux-lvm] metadata device too small Ede Wolf
2020-01-11 22:00 ` Ede Wolf
2020-01-11 22:07 ` Ede Wolf
2020-01-13 15:02 ` Marian Csontos [this message]
2020-01-13 16:35 ` Ede Wolf
2020-01-13 19:11 ` Zdenek Kabelac
[not found] ` <74436e16-d2f6-71a0-c264-71ce417de08c@nebelschwaden.de>
2020-01-13 21:29 ` Ede Wolf
2020-01-12 18:11 ` Zdenek Kabelac
2020-01-13 14:32 ` Gionatan Danti
2020-01-13 14:49 ` Zdenek Kabelac
2020-01-13 15:25 ` Gionatan Danti
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=bdbb0195-8b35-f732-1db8-641c3fbdc20f@redhat.com \
--to=mcsontos@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=listac@nebelschwaden.de \
/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).