From: Zdenek Kabelac <zkabelac@redhat.com>
To: device-mapper development <dm-devel@redhat.com>,
christophe.varoqui@opensvc.com
Subject: Re: sg_persist triggers block kernel event ???
Date: Sun, 04 May 2014 18:57:54 +0200 [thread overview]
Message-ID: <53667192.4060102@redhat.com> (raw)
In-Reply-To: <CABr-GnczryXtOkip_0L+0ztU2RcJ5izbucgs0GHo3DX7OFAMtg@mail.gmail.com>
Dne 3.5.2014 22:12, Christophe Varoqui napsal(a):
> Hi list,
>
> I observe this on a debian 7.5 server with a udevadm monitor running in the
> background :
>
> # sg_persist -n -k /dev/sdbh
> PR generation=0x0, there are NO registered reservation keys
>
Whoever opens device in 'read-write' mode and then closes device triggers
udev change event. (udev rescans whatever has changed on device after this)
That's how it works for many years already.
It's not a bug and some even says it's a feature....
Zdenek
prev parent reply other threads:[~2014-05-04 16:57 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
2014-05-04 18:01 ` Christophe Varoqui
2014-05-04 18:42 ` Christophe Varoqui
2014-05-04 16:57 ` Zdenek Kabelac [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=53667192.4060102@redhat.com \
--to=zkabelac@redhat.com \
--cc=christophe.varoqui@opensvc.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.