lvm move lv to different pv ,pvmove linux,lvm move lv to different pv,What you can do is transfer one or more PVs from the source VG to the target VG, with the vgsplit command. You can specify which PVs you want to transfer, or which LV (but only one at a . chloe-hudson-shoulder-bag-8. Description Product code # 180814-231 100% Genuine Leather Matching Quality of Original Chloe Production (imported from Europe) Comes with dust bag, .
Logical Volume Manager (LVM) provides a flexible and powerful way to manage storage on Linux systems. It allows you to abstract the physical storage layer and create logical volumes that can be resized, moved, and managed independently of the underlying physical hardware. One common task is moving a logical volume (LV) to a different physical volume (PV), which can be necessary for various reasons, such as:
* Hardware upgrades: Replacing an old hard drive with a new one and migrating the data.
* Load balancing: Distributing data across multiple PVs to improve performance.
* Disk failure: Moving data off a failing drive before it completely fails.
* Decommissioning: Removing a PV from the volume group (VG).
This article delves into the methods for moving an LV to a different PV using LVM, with a particular focus on a technique available in Debian Stretch (9.0) and later versions (specifically LVM2 version 2.02.168-2). This method involves combining `vgmerge`, `lvconvert`, and related commands to accomplish the task effectively. We will also discuss the differences between `pvmove` and `vgsplit`, and provide practical examples to guide you through the process.
Traditional Methods and Their Limitations
Historically, `pvmove` has been the go-to command for migrating extents from one PV to another within the *same* volume group. While `pvmove` remains a valid and useful tool, it's limited to operating within a single VG. It cannot directly move an LV to a PV belonging to a *different* VG.
The `vgsplit` command is used to create a new VG from a subset of PVs in an existing VG. It can be used in conjunction with `lvconvert` to move LVs between VGs, but the process can be complex and potentially disruptive, especially for large LVs or systems with limited downtime.
Moving LVs Across Volume Groups: A Debian Stretch (and Later) Solution
Debian Stretch (9.0) introduced, or rather solidified the usability of existing features in a convenient manner, making it more practical to move an LV from one VG to another. This method leverages `vgmerge` to temporarily combine the source and destination VGs, then uses `lvconvert` to create a mirror on the destination VG, and finally removes the original LV extents. This approach offers a relatively straightforward way to migrate data between VGs.
Prerequisites:
* Sufficient Space: The destination VG must have enough free space to accommodate the entire LV being moved.
* LVM2 Version: Ensure you are running LVM2 version 2.02.168-2 or later. You can check the version using the command: `lvm version`.
* Backup: Always back up your data before performing any LVM operations. This is crucial in case of unexpected errors or data loss.
Steps:
1. Identify the Source and Destination VGs and PVs:
First, you need to identify the source VG (where the LV currently resides), the destination VG (where you want to move the LV), and the specific PV(s) in the destination VG that will host the LV. You can use the following commands:
```bash
vgs # Display volume group information
pvs # Display physical volume information
lvs # Display logical volume information
```
For example, let's say:
* Source VG: `vg01`
* Destination VG: `vg02`
* LV to move: `lv_data` (residing in `vg01`)
* Destination PV: `/dev/sdb1` (belonging to `vg02`)
2. Temporarily Merge the Volume Groups:
The `vgmerge` command combines two VGs into one. This allows LVM to treat the PVs in both VGs as part of a single storage pool. The syntax is:
```bash
vgmerge
```
In our example:
```bash
vgmerge vg02 vg01
```
This command merges `vg01` into `vg02`. After this command, all PVs and LVs from `vg01` will appear as if they are part of `vg02`. Important: Make sure the target VG (`vg02` in this case) is active and has sufficient free space. Also, the source VG (`vg01`) must be deactivated if any LVs within it are active. You may need to use `lvchange -an /dev/vg01/` to deactivate the logical volumes.
3. Convert the LV to a Mirrored LV on the Destination PV:
Now that the VGs are merged, you can use `lvconvert` to create a mirror of the LV on the destination PV. This will effectively copy the data from the original location to the new PV. The `--mirrors 1` option creates a single mirror, effectively duplicating the data. The `--alloc anywhere` option is crucial because it allows the mirror to be created on the PV in the merged VG, even though it was originally part of a different VG.
```bash
lvconvert -m 1 --mirrorlog core -n lv_data_mirror /dev/vg02/lv_data /dev/sdb1
lvm move lv to different pv $149.15
lvm move lv to different pv - pvmove linux