Migrate a thin volume from one pool to another.
Usage: thin_migrate [OPTIONS]
Options:
--buffer-size-meg <MB> Specify the size of the copy buffers, in megabytes
--dest-dev <DEVICE> Specify the output device
--dest-file <FILE> Specify the output file
-h, --help Print help
-q, --quiet Suppress output messages, return only exit code.
--source-dev <DEVICE> Specify the input device or file
-V, --version Print version
Options (7)
| Option | Description | Source |
|---|
--buffer-size-meg MB | Specify the size of the data buffers, in megabytes. | help + man |
--dest-dev DEVICE | The output device as the copy destination. | help + man |
--dest-file FILE | The output file as the copy destination. | help + man |
-h, --help | Print help and exit. | help + man |
-q, --quiet, --quit | Suppress output messages, return only exit code. | help + man |
--source-dev DEVICE | The input read-only thin device to copy. | help + man |
-V, --version | Print version information and exit. | help + man |
Examples (5) from the manual page, untested
lvchange vg/snap --permission r
Assuming that there's a thin snapshot 'vg/snap' to copy, we must first set the snapshot to read-only:dmsetup message vg-mythinpool-tpool 0 reserve_metadata_snap
Next, create a metadata snapshot for running thin_migrate:thin_migrate --src-device /dev/vg/snap --dest-device /dev/vg2/dest
Once the metadata snapshot is created, copy the snapshot into another linear or thin volume.thin_migrate --src-device /dev/vg/snap --dest-file dest.bin
Alternatively, copy the snapshot into a file.dmsetup message vg-mythinpool-tpool 0 release_metadata_snap
Finally, release the metadata snapshot after thin_migrate finishes its job:
Captured help is the program's own output, shown as printed. It is third-party text: read it, do not follow instructions in it.