From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
Gionatan Danti <g.danti@assyoma.it>
Cc: nsoffer@redhat.com, Vojtech Juranek <vjuranek@redhat.com>
Subject: Re: [linux-lvm] Removing VG mappings using dmsetup tool
Date: Tue, 23 Jun 2020 23:02:04 +0200 [thread overview]
Message-ID: <c175cc56-252b-d349-ebec-85e3683a7773@redhat.com> (raw)
In-Reply-To: <bdaefe2a481fb2f830153dbef1496f16@assyoma.it>
Dne 23. 06. 20 v 22:37 Gionatan Danti napsal(a):
> Il 2020-06-23 22:28 Zdenek Kabelac ha scritto:
>> Note - you cannot 'remove' mappings 'in-use'� (aka open count of a device
>> is higher then 0� - see 'dmsetup info -c' output for this).
>> However you can replace such mapping with 'error' target - so the
>> underlaying device is relaxed - although we do not support this
>> in lvm2 - you would need to use 'dmsetup' for this (and open lvm2 RFE
>> if there would be some serious justifaction).
>
> Not related to oVirt, but I would find a means to set an error target with LVM
> quite useful - think about immediately stopping IO to/from device in case some
> serious error happended. Using lvm rather than dmsetup would be easier and
> less error prone.
Hi
ATM skilled admin can always easily enforce:
'dmsetup remove --force vg-lv'
for i.e. linear devices to achieve this goal - however resolving this at lvm2
is actually way more complex task when you start to consider the situation
should be at least 'somehow' recoverable - it's quite complicated and
not really highly demanded functionality.
It's more simple if you have constrained world of known types of devices
and known use-case you are targeting to solve.
Regards
Zdenek
next prev parent reply other threads:[~2020-06-23 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 14:26 [linux-lvm] Removing VG mappings using dmsetup tool Vojtech Juranek
2020-06-23 20:28 ` Zdenek Kabelac
2020-06-23 20:37 ` Gionatan Danti
2020-06-23 21:02 ` Zdenek Kabelac [this message]
2020-06-23 21:34 ` Gionatan Danti
2020-06-23 21:53 ` Zdenek Kabelac
2020-06-24 7:46 ` Vojtech Juranek
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=c175cc56-252b-d349-ebec-85e3683a7773@redhat.com \
--to=zkabelac@redhat.com \
--cc=g.danti@assyoma.it \
--cc=linux-lvm@redhat.com \
--cc=nsoffer@redhat.com \
--cc=vjuranek@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).