[dm-devel] multipathd can fail to monitor paths in some corne r cases

[goggin, edward]

On Fri, 01 Jul 2005 23:48:21 +0200
christophe varoqui <christophe.varoqui at free.fr> wrote

> Would you adhere to this variant ?
>
> ... because :
>
> 1) disass*table is always called before disass*status
> 2) saves a couple of loops
>
> Anyway, did you solve your git problems ?
> Your testing would be much appreciated on HEAD.

I'm able to at least check out the git head -- haven't
tried updating it yet though.

I tested your code on the git head and it works well.

I ran into other issues (mostly SuSE kernel) which is
why its taken me so long to validate.  Sorry!

What about also handling paths which are attached to the
kernel (already scanned by LLDD) but not usable when multipath(8) is
run but which could be detected to be usable by multipath?
This would involve multipathd determining a path's UID and
trying to match it with any known multipath map.  If it
didn't find one it could create and populate it -- effectively
doing the discovery process done by multipath(8).

Would require a library interface to the getuid functions like
scsi_id.  May be too much investment for little return though :((

Ed