* how to determine polling and dmeventd monitoing state?
@ 2012-07-10 20:55 ben
2012-07-10 22:54 ` Alasdair G Kergon
0 siblings, 1 reply; 3+ messages in thread
From: ben @ 2012-07-10 20:55 UTC (permalink / raw)
To: lvm-devel
I know that I can look through the deamon log to see if dmeventd ismonitoring
a volume but is there any practical way for a program to query the system to
get that information? Is the polling status displayed or accessable anywhere?
I certainly can't find it. Thank you.
Thank you.
benscott at nwlink.com
^ permalink raw reply [flat|nested] 3+ messages in thread
* how to determine polling and dmeventd monitoing state?
2012-07-10 20:55 how to determine polling and dmeventd monitoing state? ben
@ 2012-07-10 22:54 ` Alasdair G Kergon
2012-07-11 7:09 ` Peter Rajnoha
0 siblings, 1 reply; 3+ messages in thread
From: Alasdair G Kergon @ 2012-07-10 22:54 UTC (permalink / raw)
To: lvm-devel
On Tue, Jul 10, 2012 at 01:55:30PM -0700, ben wrote:
> I know that I can look through the deamon log to see if dmeventd ismonitoring
> a volume but is there any practical way for a program to query the system to
> get that information? Is the polling status displayed or accessable anywhere?
> I certainly can't find it. Thank you.
Good point. It's available internally through
seg->segtype->ops->target_monitored()
and we need to expose this through lvs.
Alasdair
^ permalink raw reply [flat|nested] 3+ messages in thread
* how to determine polling and dmeventd monitoing state?
2012-07-10 22:54 ` Alasdair G Kergon
@ 2012-07-11 7:09 ` Peter Rajnoha
0 siblings, 0 replies; 3+ messages in thread
From: Peter Rajnoha @ 2012-07-11 7:09 UTC (permalink / raw)
To: lvm-devel
On 07/11/2012 12:54 AM, Alasdair G Kergon wrote:
> On Tue, Jul 10, 2012 at 01:55:30PM -0700, ben wrote:
>> I know that I can look through the deamon log to see if dmeventd ismonitoring
>> a volume but is there any practical way for a program to query the system to
>> get that information? Is the polling status displayed or accessable anywhere?
>> I certainly can't find it. Thank you.
>
> Good point. It's available internally through
> seg->segtype->ops->target_monitored()
> and we need to expose this through lvs.
In addition to that, we could also revive the 'dmevent_tool'
that is a part of the dmraid at the moment and include this one in
lvm2 upstream (probably as a part of dmsetup or dmeventd or a separate
tool even). Existing tool from dmraid upstream is supposed to show dm
devices in general and their status with respect to dmeventd monitoring.
Though the tool itself needs a bit of a cleanup before porting.
There's also a bugzilla report open for this functionality:
https://bugzilla.redhat.com/show_bug.cgi?id=805425
Peter
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-07-11 7:09 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-07-10 20:55 how to determine polling and dmeventd monitoing state? ben
2012-07-10 22:54 ` Alasdair G Kergon
2012-07-11 7:09 ` Peter Rajnoha
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.