Filter
Top Products
Chapter 4 StorEdge File Replicator 4-13
To stop mirroring on a volume, the user must "break" the mirror. The mirror can be
broken from either the master or mirror system. When the mirror is broken, it enters
the BREAKING state until the last file system transactions in transit have been
acknowledged, and the break request has been communicated to both master and
mirror. Data transfer between master and mirror is then stopped, the mirror
definition is removed from the mirror service, and the mirror buffer is removed on
the master volume. The mirror volume remains mounted as a read-only NBD
volume. A broken mirror can be restarted at any time, but must go through the
entire creation and replication process from the beginning.
4.2.6 Cannot perform first-time synchronization of
mirror system:
File system activity on the master system must be stopped or reduced to a very low
level. It is much more filesystem intensive to synchronize the mirror for the first time
than it is to maintain it.
4.2.7 Filesystem errors, such as run check, directory
broken, etc.:
StorEdge File Replicator is designed to immediately break any active mirrors to a
volume with filesystem problems, to avoid replicating these errors. The errors must
be corrected via the fsck procedure before reestablishing the mirror.
4.2.8 Error messages, panics or hang condition when
enabling mirror:
Ensure that the master and mirror systems are running the same version of the
StorEdge operating system.