From: Peter Rajnoha <prajnoha@redhat.com>
To: lvm-devel@redhat.com
Subject: master - dmsetup: add warning
Date: Tue, 27 May 2014 09:00:50 +0200 [thread overview]
Message-ID: <53843822.1080102@redhat.com> (raw)
In-Reply-To: <20140526213220.BF35F60DC8@fedorahosted.org>
On 05/26/2014 11:32 PM, Zdenek Kabelac wrote:
> Gitweb: http://git.fedorahosted.org/git/?p=lvm2.git;a=commitdiff;h=3cb2658fb7ff0bba45e66e79bce8812c819dff52
> Commit: 3cb2658fb7ff0bba45e66e79bce8812c819dff52
> Parent: 6e9105c7bb7f4a1beb34579303670e4510c7d2e6
> Author: Zdenek Kabelac <zkabelac@redhat.com>
> AuthorDate: Mon May 26 22:51:04 2014 +0200
> Committer: Zdenek Kabelac <zkabelac@redhat.com>
> CommitterDate: Mon May 26 22:56:30 2014 +0200
>
> dmsetup: add warning
>
> Warn when --udevcookie/DM_UDEV_COOKIE is used with 'dmsetup remove --force'.
>
> When command is doing multiple ioctl operations on a single device,
> it may invoke udev activity, that is colliding with further ioctl commands.
> The result of such operation becomes unpredictable.
> Use of --retry could partially help...
We could add proper flags to skip all the scanning in udev in case we're
resuming the mapping with error target for the "remove --force"...
--
Peter
prev parent reply other threads:[~2014-05-27 7:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 21:32 master - dmsetup: add warning Zdenek Kabelac
2014-05-27 7:00 ` Peter Rajnoha [this message]
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=53843822.1080102@redhat.com \
--to=prajnoha@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.