Filesystem crash

[Slawomir Gora]

Hi,

In MC/SG enviroment I activate my vg:

vgchange -a e -s -q n vgtest1

vgtest has lvols mirrored between two luns on
different storages (ESS1 and ESS2)
when we are performing tests - shutdown/startup
of one storage, shut/start FC switches -
filesystem /dev/vgtest1/lvol1 become corrupt
and serwer reboots.

Is this vg activation ( -s ) correct ?

[Bernhard Mueller]

Hi,

man vgchange:
-s disables the synchronization of stale extents.

you should not use that option.

Still if one of the storages fails you should be aware that after it comes up again you should issue vgchange -a e to recover missing links and sync the extents.


Regards,
Bernhard

[Slawomir Gora]

In MC/SG control script is
# Uncomment the second line (VGCHANGE="vgchange -a e -q n -s"), and comment
# out the default, if your disks are mirrored on separate physical paths,
# and you want the mirror resynchronization to ocurr in parallel with
# the package startup.