[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [dm-devel] blacklist issues and more



On mar, 2005-06-21 at 15:50 -0400, goggin, edward wrote:

> 
> (2) This isn't even sufficient since the multipathd holds an open on each
> multipath mapped
> device.  One result of this is that the target devices used by the mapped
> device are not
> available for use by any application which must "claim" them exclusively,
> for example,
> mount(8) or for use via raw io.  I must kill multipathd before I can use any
> of the target
> devices by these "claiming" applications.  Seems like multipath should get
> multipathd
> to close its open on the newly blacklisted block device.
> 
I guess it may be related to the wait DM event ioctl.

The daemon can't reap the waiting threads it starts (may be I'm just too
ignorant there), as they are blocked in the ioctl. It's a known and
serious problem. Moreover the daemon leaks here and pins the dm-* kobj.

The dmeventd should help fix these problems, but I was waiting more
input from Alasdair before deciding to merge that in the 0.4.5 dev
cycle.

Can you confirm this analysis applies to your reported problem.

Regards,
-- 
christophe varoqui <christophe varoqui free fr>



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]