xp256 split runs into errors

[Edgar_8]

Hi,

We have an XP256 array & we synchronized the BC vg's but when the BC vg's were in PAIRED status & we issued a split command, during the fsck phase the below error is prompted & the split fails:

Now we need to mount the new logical volumes on the BC mount points
log replay in progress
vxfs fsck: file system does not contain a valid log
vxfs fsck: cannot perform log replay
file system is not clean, full fsck required
full file system check required, exiting ...
vxfs mount: /dev/vg_name/lvol1 is corrupted. needs checking
ERROR: The command - mount /dev/vg_name/lvol1 /mount_pt failed.

Anyone have any ideas on resolution?

Thanks in advance.

[Edgar_8]

Hi,

Does anyone out there have any advice as to resolving this problem?

Thanks in advance!

[Robert Young_9]

The XP256 Business Copy will copy all the LVM header information so if the BC volume group is on the same server as the original, you need to change the volume group ID on all the disks in the BC volume group. (This is not the same as the /dev/vgBC/group file.)

First, do a ls -l /dev/vgBC/group and record the info because you will need to re-create this file later.

Now you will need to export the BC volume group before doing the split. Use the vgexport command with the -m and -f options to preserve the logical volume names and disk info.

Then do the split. (If you can unmount the file systems in the original volume group before doing the split, then you won't have to do a fsck on the BC later)

When the split is complete you need to do a vgchgid on all the disks in the BC volume group. This is to make the VGID unique. If you don't do this you will not be able to access the BC volume group on the same server as the original.

Now re-create the /dev/vgBC directory and use mknod to re-create the group file.

Now do a vgimport with the -m and -f options to import the BC volume group with the new vg id.

Activate the BC volume group using vgchange -a y vgname

Now you should be able to access the logical volumes.

If the BC volume group is on a different server, you only need to deactivate the BC volume group before doing the split, then reactivate it after.