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

Re: [dm-devel] multipath state discrepancies between user and kernel space



On ven, 2005-07-01 at 17:30 -0400, goggin, edward wrote:
> 
> (1) In the event that automatic path group failback is not configured, which
> value for the highest
> priority path group should be displayed by "multipath -l" -- the one used by
> the multipath target
> driver in the kernel or the path group which is actually the highest
> priority path group at that
> moment in time?  Or both -- or still do (see issue (2) below) for path
> state?
> 
> The notion of highest priority path group in the kernel may be different
> from the actual highest
> priority path group in a case whereby:
> 
> (a)	auto failback is not enabled
> (b) 	all paths to the highest priority path group are failed
> (c) 	multipath is run manually -- causing path group switching to another
> path group
> (d) 	one or more of the paths that were had failed are now made active
> again -- yet
> 	because auto failback is not enabled, this path group is not made
> the highest
> 	priority path group in the kernel, although by definition it is the
> highest priority
> 	path group
> 
Would printing the "PG-summed path priorities" value for each PG meet
your needs/taste ?

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



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