From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zdenek Kabelac Subject: Re: sg_persist triggers block kernel event ??? Date: Sun, 04 May 2014 19:23:25 +0200 Message-ID: <5366778D.90109@redhat.com> References: <536670DF.2040605@suse.de> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <536670DF.2040605@suse.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: device-mapper development List-Id: dm-devel.ids 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