What happens if a load Sharing (LS) mirror replies a Vserver root volume to any node in the cluster and you promote one of the mirror destinations?

When an LS mirror destination is promoted to become the new source, the original source volume transitions from read-write to a mirror destination state while the promoted volume becomes the new read-write source. During this promotion and resynchronization window, the volume state change results in clients temporarily having read/write access to the root volume instead of the normal read-only replicated access. This temporary disruption is why LS mirror promotion must be planned carefully, as it alters the expected access model for the root namespace.

Promoting an LS mirror does not prevent the original source from becoming stale; the original source transitions to a mirror destination and may itself require resynchronization, making it susceptible to becoming stale if the process is disrupted.

The documented behavior is not a forced client remount but rather a temporary change in access mode to read/write; clients do not necessarily lose their mount points during the promotion.

LS mirror promotion is not a non-disruptive operation; the volume state change during the promotion process causes a temporary disruption where clients gain read/write access, which is abnormal and unintended behavior for a root volume.