Comment 59 for bug 557429

On 4/23/2010 6:52 AM, ceg wrote:
> I'd suggest to consider the following option about whether to assemble
> segments known to contain conflicting changes or not:
>
> AUTO -SINGLE_SEGMENTS_WITH_KNOWN_ALTERNATIVE_VERSIONS

As I have said, if you want another component to automatically notice
when one of the disks has been ejected from the array due to conflicting
changes and migrate it to a new array, that is quite fine. It would
then show up as a new mount on your desktop.

> It seems you consider segments being available one at a time, then on
> some incidence eventually together, and then one at a time again later
> would indicate a not-mainly-theoretical failure type and it should be
> handled by always auto-removing all but the first segment on the
> incidence. (So they won't get auto assembled anymore.)
>
> Let's conclude this is OK, for part of the users. (Mostly those that
> want to be sure and manage their arrays issuing commands by hand.)
>
> But it does pose a problem if you want to support managing array segments
> by just plugging disks and occasionally commanding
> simple sync directives (eventually just by right clicking on the
> segments showing up on the desktop).

Even if you intentionally caused the divergence you don't want both
disks to show up as the same volume when plugged in. One of them should
be renamed so it is clear that they are not the same anymore, and if you
do connect them both, then both should show up -- as separate volumes.