From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] disabling udev_sync and udev_rules
Date: Tue, 15 Mar 2016 23:56:17 +0100 [thread overview]
Message-ID: <56E89311.1030408@gmail.com> (raw)
In-Reply-To: <fd77879855874fabb6174e3c2d5b54e0@XCH-ALN-006.cisco.com>
Dne 15.3.2016 v 23:31 Serguei Bezverkhi (sbezverk) napsal(a):
> Hello folks,
>
> While trying to make lvm work within a docker container I came across an issue when all lvcreate/lvremove got stuck indefinetly or until control-c. When I checked process I noticed lvm was waiting on one semaphore, I found that other folks hit similar issue and they fixed it by setting udev_sync and udev_rules to 0. It also helped my case too.
>
> I would greatly appreciate if you could share your thought if this change in future can potentially have any negative impact.
>
> Thank you
Hi
To 'unblock' stuck processes waiting on udev cookie - you could run:
'dmsetup udevcomplete_all'
However the key question is - how you could get stuck.
That may need further debugging.
You would need to expose your OS version and also version of lvm2 in use.
Non working cookies are bad - and disabling udev sync is even more bad idea...
Regards
Zdenek
next prev parent reply other threads:[~2016-03-15 22:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 22:31 [linux-lvm] disabling udev_sync and udev_rules Serguei Bezverkhi (sbezverk)
2016-03-15 22:56 ` Zdenek Kabelac [this message]
2016-03-15 23:13 ` Serguei Bezverkhi (sbezverk)
2016-03-15 23:52 ` Steven Dake (stdake)
2016-03-16 8:06 ` Zdenek Kabelac
2016-03-16 13:37 ` Steven Dake (stdake)
2016-03-16 15:05 ` Zdenek Kabelac
2016-03-16 15:11 ` Serguei Bezverkhi (sbezverk)
2016-03-16 15:42 ` John Stoffel
2016-03-16 16:17 ` Serguei Bezverkhi (sbezverk)
2016-03-16 16:53 ` Zdenek Kabelac
2016-03-16 16:58 ` Steven Dake (stdake)
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=56E89311.1030408@gmail.com \
--to=zdenek.kabelac@gmail.com \
--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 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.