Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

csunique(8) [mojave man page]

CSUNIQUE(8)						    BSD System Manager's Manual 					       CSUNIQUE(8)

NAME
csunique -- modify the UUIDs of CoreStorage metadata objects SYNOPSIS
csunique [-v | --verbose] [-n | --dry-run] [-I | --include include] [-X | --exclude exclude] device ... DESCRIPTION
The csunique utility can rewrite CoreStorage logical volume group metadata, changing object UUIDs. All CoreStorage objects are uniquely identified by UUIDs. This can be useful when copying an initial "canned image" onto multiple machines to establish these as independent vol- umes. The device parameter(s) should be path(s) to the "raw" (character special) disk device(s) such as /dev/rdisk1s1 that constitute the CoreStor- age logical volume group. If you specify a "non-raw" (block special) path such as /dev/disk1s1, or just the disk name such as disk1s1, it will automatically be converted to the corresponding raw disk device (/dev/rdisk1s1). The options are as follows: -v Output verbose progress information of each step and the UUID re-mappings. -n Operates in "dry run" mode; no changes are made to the on-disk data. -I Specifies an additional class of UUID objects that should be modified. -X Specifies a class of UUID objects that should not be modified. By default all UUIDs will be changed. The classes of CoreStorage UUID objects that can be included or excluded from modification by csunique are indicated using the following characters: f logical volume family (LVF) g logical volume group (LVG) l logical volume (LV) p physical volume (PV) w MLV wipekey csunique processes/transforms the CoreStorage metadata in a number of steps: 1. Firstly, an initial fsck_cs is performed to ensure the source structure is consistent; 2. If the LVG is currently live and mounted by the kext it is temporarily "frozen"; 3. If the disk partitions are of type Apple_CoreStorage then they are switched offline (which dissociates the kext from the old meta- data); 4. The CoreStorage metadata is locally parsed and loaded; 5. All object UUIDs are located, and new UUIDs generated for classes as set by the -I and -X options; 6. UUIDs are re-written to disk; 7. A post-modification fsck_cs is performed to ensure the final structure is consistent; 8. Finally, any disk partitions taken offline are restored to Apple_CoreStorage (which will reload the kext with the new UUID meta- data). DIAGNOSTICS
The csunique utility exits with 0 if the CoreStorage logical volume group was modified as directed, and with >0 if it was unable to do so. Any error message is written to stderr. BUGS
csunique cannot modify the LVF UUID if there are any encrypted LVs inside it. Any mounted LVs must be manually unmounted before invocation. HISTORY
The csunique utility first appeared in OS X 10.8.1. OS X
September 25, 2012 OS X

Check Out this Related Man Page

vgrestore(1M)															     vgrestore(1M)

NAME
vgrestore - restore a VxVM disk group back to an LVM volume group SYNOPSIS
/etc/vx/bin/vgrestore vg_name DESCRIPTION
The vgrestore command restores a Logical Volume Manager (LVM) volume group that was previously converted to a VxVM disk group by the vxvm- convert utility. ARGUMENTS
vg_name Specifies the name of a volume group that was converted to a VxVM disk group by the vxvmconvert utility. EXIT CODES
vgrestore exits with one of the following values: 0 Successful completion. >0 Failure; an error occurred. WARNINGS
vgrestore functions only on VxVM disk groups that were converted from LVM volume groups by the vxvmconvert command. It is a good idea to back up user data before running vgrestore, and restore it after the vgrestore completes, as vgrestore can only restore a logical volume back to the state it was in before conversion to VxVM. If data changed on the volume while it was a VxVM volume, the changes won't be reflected on the volume after being restored to LVM. As part of the original conversion process, applications that once referenced the now-converted LVM volume's path names may have changed to reference VxVM volume special device file names. Alternatively, special device file path names originally representing the now-converted LVM volumes may have changed to symbolic links pointing to the VxVM volume path names. Be sure to undo these actions when restoring back to LVM. Do not use vgrestore unless you are certain that you want to restore LVM volume groups. After vgrestore this is run, the VxVM disks will no longer exist. EXAMPLES
To restore the LVM volume group vg03 that was converted by vxvmconvert to the VxVM disk group dg03, enter: vgcfgrestore vg03 SEE ALSO
vxvmconvert(1M) Veritas Volume Manager Migration Guide VxVM 5.0.31.1 24 Mar 2008 vgrestore(1M)
Man Page