cmcheckconf - "cross-link device"

[Steven Hargus]

Hello -
I am preparing to set up a cluster. When I run cmcheckconf -v -k -C cmclconf.ascii, I get the following results:
Checking cluster file: cmclconf.ascii
Checking nodes ... Done
Checking existing configuration ...
Done
Gathering configuration information .............. Done
Error: Volume group /dev/vgora42a01 currently belongs to another cluster.
It cannot be included in this one.
Error: Volume group /dev/vgora42b01 currently belongs to another cluster.
It cannot be included in this one.
Error: Volume group /dev/vgora42c01 currently belongs to another cluster.
It cannot be included in this one.
Error: Volume group /dev/vgora42d01 currently belongs to another cluster.
It cannot be included in this one.
Error: Volume group /dev/vgora43b01 currently belongs to another cluster.
It cannot be included in this one.
cmcheckconf : Unable to verify cluster file: cmclconf.ascii.
Cross-device link.
Checking for inconsistencies .. Done
Maximum configured packages parameter is 30.
Configuring 0 package(s).

I know where the "Volume belongs to another cluster" message is coming from - I think I should be able to fix that with vgchange -c n .

What I am wondering is what the "Cross-device link." message means?

[Animesh Chakraborty]

Hi ,
"cross device link" -This problem usually occurs because two VGs claim ownership for the
same disk.
and also check for duplicate minor number.
#ll /dev/*/group
After deactivating the vg, the cross device link error should not come.

Regards
Animesh

[Sanjay_6]

Hi Steven,

Deactivating the cluster information of the vg /dev/vgora42b01 might help remove the cross-link message.

Here is a thread on cross-device link which might help you in sorting out the problem.

http://us-support.external.hp.com/cki/bin/doc.pl/sid=3ddb45b91720b6d29d/screen=ckiDisplayDocument?docId=200000050664888

Hope this helps.

thanks

[Steven Hargus]

All -
I am waiting to hear from management to schedule an outage so I can give these a try. Sounds like deactivating the cluster ownership should do the trick, but I'll need to shut down the applications to try it out. If it doesn't work, I'll put a call in to the RC.

[Insu Kim]

When I saw "Cross-link device", Below is what I'm doing.
(cros-link device maans usually means LVM config structures on pv are wrong or corrupt)

If Affected volume is vg02 with /dev/dsk/c0t0d0,
1, need information about how many lvols are created in the volume group and the exact size information when they're created.

2. vgexport vg02
3. pvcreate vg02 with /dev/rdsk/c0t0d0
4. vgcreate vg02 with /dev/dsk/c0t0d0
5. lvcreate lvols with the exact size and lvol name when they were created before.
5. try "cmcheckconf" again.

Before doing this, making a full backup for the affected volume group is neccessary.


Hope this helps,

[Insu Kim]

One more thing is,
Do not newfs on lvols after lvcreating lvols.
Your data will be blown out.

[Steven Hargus]

In-Su Kim -
Doesn't each of those steps (pvcreate, vgcreate, lvcreate) ensure complete destruction of the volume group and all of the data contained therein? Avoiding the newfs would be pointless...