3.3.7 How to Assign a New Minor Number to a Disk Device Group (VERITAS Volume Manager)

If registering a VxVM disk device group fails due to a minor number conflict with another disk group, the new disk group must be assigned a new, unused minor number. After assigning the new minor number, you then rerun the procedure to register the disk group as a Sun Cluster disk device group.

1. Become superuser on a node of the cluster.

2. Determine the minor numbers in use.

   # ls -l /dev/vx/dsk/*

3. Choose any other multiple of 1000 that is not in use as the base minor number for the new disk group.

4. Assign the new minor number to the disk group.

   # vxdg reminor diskgroup base_minor_number

3.3.7.1 Example--How to Assign a New Minor Number to a Disk Device Group

This example shows the minor numbers 16000-16002 and 4000-4001 being used. The vxdg reminor command is used to reminor the new disk device group to use the base minor number 5000.

# ls -l /dev/vx/dsk/*
/dev/vx/dsk/dg1
brw-------   1 root     root      56,16000 Oct  7 11:32 dg1v1
brw-------   1 root     root      56,16001 Oct  7 11:32 dg1v2
brw-------   1 root     root      56,16002 Oct  7 11:32 dg1v3
 
/dev/vx/dsk/dg2
brw-------   1 root     root      56,4000 Oct  7 11:32 dg2v1
brw-------   1 root     root      56,4001 Oct  7 11:32 dg2v2
# vxdg reminor dg3 5000

3.3.7.2 Where to Go From Here

The VxVM disk group must be registered as a Sun Cluster disk device group. See "3.3.8 How to Register a Disk Group as a Disk Device Group (VERITAS Volume Manager)".