In principle it is possible to create FSes on shared volume groups with cluster methods (also known as C-SPOC), either from the command line or using the respective SMIT menus. In practice, however, many options are missing in the C-SPOC variants. For instance, it is not possible to add a mountgroup to a newly created FS.

Many (me included) rely therefore on non-cluster methods (the normal crfs-command, et. al.) even in cluster environments. One common method, using the non-documented command imfs, is like this (we are supposing a two-node active/passive-cluster here):

Code:

root@activenode # crfs ....
root@passivenode # varyonvg -ncA <sharedvg>
root@passivenode # imfs <sharedvg>
root@passivenode # varyonvg -ncP <sharedvg>

This will not work any more with HACMP 7.1.3 upwards because IBM introduced a new (and very badly documented) fencing mechanism. If you try the above on a newer cluster you will immediately find the disks in <sharedvg> in the errpt as missing. The only method to get clear from this is to cycle the cluster completely.

Instead use the following method now:

Code:

root@activenode # crfs ....
root@passivenode # /usr/es/sbin/cluster/events/utils/cl_set_vg_fence_height -c <sharedvg> rw
root@passivenode # varyonvg -ncA <sharedvg>
root@passivenode # imfs <sharedvg>
root@passivenode # varyonvg -ncP <sharedvg>
root@passivenode #  /usr/es/sbin/cluster/events/utils/cl_set_vg_fence_height -c <sharedvg> ro

If you want to try the - old and new - method use a cluster you can afford to powercycle. There, you will be able to watch the problem unfold in hacmp.out - or the C-SPOC log, if you have used it.

I hope this helps.

bakunin
________________________
Sources: