From: Mike Snitzer <snitzer@redhat.com>
To: lvm-devel@redhat.com
Subject: [RFC][PATCH] never scan a device which is using the error target
Date: Sun, 24 Oct 2010 13:28:40 -0400 [thread overview]
Message-ID: <20101024172840.GA2384@redhat.com> (raw)
In-Reply-To: <4CC4623D.7080505@redhat.com>
On Sun, Oct 24 2010 at 12:43pm -0400,
Milan Broz <mbroz@redhat.com> wrote:
> On 10/24/2010 02:55 AM, Mike Snitzer wrote:
> > A merged snapshot's DM device is made to use the "error" target as part
> > of lvm's transaction to merge a snapshot. This snapshot merge use-case
> > aside, any device using the error target shouldn't be scanned.
> >
> > NOTE: I'm not using an ignore_suspended_devices() check like other
> > target checks in device_is_usable() -- its not clear to me what such a
>
> IIRC scan for mirrors, snapshots etc is OK.
> But during mirror repair or conversion some devices in the middle of stack
> can be suspended, so the ignore_suspended_devices() says when it is safe to
> scan it. (see that it is set during conversions etc)
> IMHO it is quite hack (mainly for clusters where one node runs the conversion
> or repair and other just follows the state).
OK, thanks for the info.
> For error device it makes no sense - it is unusable all the time:-)
Right.
> > + if (target_type && !strcmp(target_type, "error")) {
>
> Do we have some #define for the error target name?
I don't think we have a #define for any target names. Target names are
open coded strings throughout the lvm2 codebase. Certainly a candidate
for cleanup.
> Anyway, ack.
Thanks,
Mike
next prev parent reply other threads:[~2010-10-24 17:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-24 0:55 [RFC][PATCH] never scan a device which is using the error target Mike Snitzer
2010-10-24 16:43 ` Milan Broz
2010-10-24 17:28 ` Mike Snitzer [this message]
2010-10-25 1:00 ` Alasdair G Kergon
2010-10-25 1:23 ` Mike Snitzer
2010-10-25 1:24 ` Alasdair G Kergon
2010-10-25 6:19 ` Milan Broz
2010-10-25 18:59 ` Alasdair G Kergon
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=20101024172840.GA2384@redhat.com \
--to=snitzer@redhat.com \
--cc=lvm-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.