From: Gionatan Danti <g.danti@assyoma.it>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Alexander 'Leo' Bergolth <leo@strike.wu.ac.at>
Subject: Re: [linux-lvm] unable to recover from degraded raid1 with thin pool (was: activation mode=degraded doesn't work with thin pool)
Date: Fri, 20 Oct 2017 23:06:30 +0200 [thread overview]
Message-ID: <0f68ed1ad140673541aa8a896b78de6e@assyoma.it> (raw)
In-Reply-To: <378f8596-dfae-2557-a53f-b614940bba22@strike.wu.ac.at>
Il 19-10-2017 13:45 Alexander 'Leo' Bergolth ha scritto:
> On 10/17/2017 03:45 PM, Alexander 'Leo' Bergolth wrote:
>> I just tested lv activation with a degraded raid1 thin pool.
>> Unfortunately it looks like activation mode=degraded only works for
>> plain raid1 lvs. If you add a thin pool, lvm won't activate it in
>> degraded mode. (Unless you specify --activationmode partial, which is
>> IMHO rather dangerous.)
>
> Unfortunately I cannot even replace a faulty PV if a thin pool is
> present.
From you command history, I can see you are trying to remove the failed
device (to re-add a good device later).
Instead, can you try with lvconvert --repair or lvconvert --replace? Do
they works?
Thanks.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
next prev parent reply other threads:[~2017-10-20 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 13:45 [linux-lvm] activation mode=degraded doesn't work with thin pool Alexander 'Leo' Bergolth
2017-10-19 11:45 ` [linux-lvm] unable to recover from degraded raid1 with thin pool (was: activation mode=degraded doesn't work with thin pool) Alexander 'Leo' Bergolth
2017-10-20 21:06 ` Gionatan Danti [this message]
2017-10-23 13:26 ` [linux-lvm] unable to recover from degraded raid1 with thin pool Alexander 'Leo' Bergolth
2017-10-27 10:13 ` Alexander 'Leo' Bergolth
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=0f68ed1ad140673541aa8a896b78de6e@assyoma.it \
--to=g.danti@assyoma.it \
--cc=leo@strike.wu.ac.at \
--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).