On Fri, Feb 26, 2016 at 12:32:51AM +, Shiva Krishna wrote:
>
>
> On 2/25/16, 12:49 PM, "Benjamin Marzinski" wrote:
>
> >On Sat, Feb 20, 2016 at 08:23:29PM +, Shiva Krishna wrote:
> >
> >I understand your problem, but this isn't the right patch to fix it. For
> >one
On 02/26/2016 04:49 AM, Benjamin Marzinski wrote:
> On Sat, Feb 20, 2016 at 08:23:29PM +, Shiva Krishna wrote:
>
> I understand your problem, but this isn't the right patch to fix it. For
> one this check
>
> + if (newstate != PATH_GHOST || pp->mpp->nr_active > 0 ||
> +
On 2/25/16, 12:49 PM, "Benjamin Marzinski" wrote:
>On Sat, Feb 20, 2016 at 08:23:29PM +, Shiva Krishna wrote:
>
>I understand your problem, but this isn't the right patch to fix it. For
>one this check
>
>+ if (newstate != PATH_GHOST || pp->mpp->nr_active
On Sat, Feb 20, 2016 at 08:23:29PM +, Shiva Krishna wrote:
I understand your problem, but this isn't the right patch to fix it. For
one this check
+ if (newstate != PATH_GHOST || pp->mpp->nr_active > 0 ||
+ pp->tpgs != TPGS_IMPLICIT) {
is pretty problematic.
multipathd treats "stand-by" path as active(ghost) and reinstate path.This
causes I/O hang issues and lots of "change" udev events in cases where only
stand-by paths are present in multipath map and target supports only implicit
tpgs mode(active/passive arrays)
This can happen during system boot