All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: sg_persist triggers block kernel event ???
Date: Sun, 04 May 2014 19:23:25 +0200	[thread overview]
Message-ID: <5366778D.90109@redhat.com> (raw)
In-Reply-To: <536670DF.2040605@suse.de>

Dne 4.5.2014 18:54, Hannes Reinecke napsal(a):
> On 05/04/2014 01:34 AM, Christophe Varoqui wrote:
>> It seems sg_persist is doing an "open rw => close" for --in commands,
>> causing a kernel change-event.
> Yep.
>
> Look for 'watch' in the udev rules, that's precisely what it's doing.
>
> (Bloody annoying if you ask me. Generally I recommend to remove that thing
> from the rules).

When watch rule is disabled/removed in  udev rules - your udev db becomes 
invalid when i.e. you run  command like  'mkfs' - since the udev db will not 
be updated to list information about newly formatted filesystem.

Of course there are many cases where disabling  watch rule makes sense
(i.e. you export lots of disks to virtual guests) - but unless you are
familiar with udev and you know what you are doing - think twice before disabling.

Zdenek

  reply	other threads:[~2014-05-04 17:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-03 20:12 sg_persist triggers block kernel event ??? Christophe Varoqui
2014-05-03 20:38 ` Christophe Varoqui
2014-05-03 21:47   ` Christophe Varoqui
2014-05-03 23:34 ` Christophe Varoqui
2014-05-04 16:54   ` Hannes Reinecke
2014-05-04 17:23     ` Zdenek Kabelac [this message]
2014-05-04 18:01       ` Christophe Varoqui
2014-05-04 18:42         ` Christophe Varoqui
2014-05-04 16:57 ` Zdenek Kabelac

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=5366778D.90109@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=dm-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.