LVM: Difference between revisions
mNo edit summary |
mNo edit summary |
||
Line 18: | Line 18: | ||
NOTE: remember to add snapshot support when calling lvcreate | NOTE: remember to add snapshot support when calling lvcreate | ||
| |||
== Raid on LVM == | == Raid on LVM == | ||
*[https://www.theurbanpenguin.com/striped-lvm-volumes/ Striped LVM volumes] | *[https://www.theurbanpenguin.com/striped-lvm-volumes/ Striped LVM volumes] | ||
*[https://www.linuxsysadmins.com/create-striped-logical-volume-on-linux/ https://www.linuxsysadmins.com/create-striped-logical-volume-on-linux/] | *[https://www.linuxsysadmins.com/create-striped-logical-volume-on-linux/ https://www.linuxsysadmins.com/create-striped-logical-volume-on-linux/] | ||
| |||
= Related commands = | = Related commands = | ||
Line 68: | Line 70: | ||
| | ||
| |||
== lvremove == | == lvremove == | ||
Line 79: | Line 82: | ||
lvremove VGname/LVname | lvremove VGname/LVname | ||
== Do you really want to remove active logical volume == | |||
lvchange -a n vgname/lvname | lvchange -a n vgname/lvname | ||
just to make sure | just to make sure | ||
Line 103: | Line 109: | ||
where size should be enough to hold the data changes | where size should be enough to hold the data changes | ||
| |||
= FAQ = | = FAQ = | ||
Line 232: | Line 238: | ||
== WARNING: Device /dev/dm-17 not initialized in udev database even after waiting 10000000 microseconds. == | == WARNING: Device /dev/dm-17 not initialized in udev database even after waiting 10000000 microseconds. == | ||
Try | Try | ||
udevadm trigger | udevadm trigger | ||
| |||
== wipefs: error: /dev/sdg: probing initialization failed: Device or resource busy == | == wipefs: error: /dev/sdg: probing initialization failed: Device or resource busy == |
Revision as of 08:44, 14 June 2021
Logical Volume Management on Linux
Links
- How do you clone an lvm partition?
- Monitoring with zabbix
- HOWTO
- Thin provisioning
- Beginner's guide to LVM
- Resizing LVM + DRBD
- http://wiki.tldp.org/LVM-on-RAID
- LVM nesting
- http://blog.gadi.cc/better-lvm-for-kvm/
- [https://www.tecmint.com/take-snapshot-of-logical-volume-and-restore-in-
- Taking a Backup Using Snapshots
NOTE: remember to add snapshot support when calling lvcreate
Raid on LVM
Related commands
lvdisplay
lvrename
lvrename groupname oldname newname
vgrename
lsblk
partprobe
lvchange
vgchange
dmsetup
vgs
create physical volume
pvcreate /dev/sda3
lvcreate
lvcreate -L12G -nmyvol myvolumegroup lvcreate -l 100%FREE -nmyvol myvolumegroup
lvresize
lvresize --resizefs -L-2G /dev/vg/foo
or grow to all remaining space vg:
lvresize -l +100%FREE /dev/myvg/myvol
lvremove
To remove all volumes in group VGname
lvremove VGname
To remove a volume
lvremove VGname/LVname
Do you really want to remove active logical volume
lvchange -a n vgname/lvname
just to make sure
Logical volume X/Y contains a filesystem in use
Could be NFS. Always remember NFS!
pvck
To find the metadata:
pvck /dev/sdb1
LVM snapshot
lvcreate --size 1G --snapshot --name snap-1 /dev/myvg/mylv
where size should be enough to hold the data changes
FAQ
Access logical volumes within logical volume
partprobe /dev/mapper/vg-mydata lsblk
This will show the (sub) partitions/volumes, then edit /etc/lvm/lvm.conf
filter = [ "a|.*/|", "a|mydata|","r|.*|" ]
Then run:
vgscan lvscan vgs
Now you should see the names of the volumes you're looking for, so now:
vgchange -a y guestsname_mydata-home
and then you should be able to
mount /dev/mapper/guestsname_mydata-home
When done, remember to change back the filter in lvm.conf, default is
filter = [ "a|.*/|" ]
and of course then once again
vgscan lvscan
vgreduce Can't remove final physical volume
Means you're trying to remove the last physical volume, instead just use
vgremove
grow logical volume
https://www.tldp.org/HOWTO/LVM-HOWTO/extendlv.html
lvextend -L+100G /dev/myvg/myvol
Add disk to volume group
pvcreate /dev/sdc vgextend MYVG /dev/sdc
And if you need space right now:
lvextend -l +100%FREE /dev/NYVG/mylv
And then grow fs
lvremove: Logical volume vg-kvm/vps-snapshot is used by another device.
Could be kpartx, see
/dev/mapper/
lvremove Logical volume foo/bar in use
check with lsof, fuser and:
losetup -l
to see if a /dev/dm-* looks familiar
some say lvchange -an the snapshot first, but that disables the lv it's connected to as well
OR
dmsetup info -c
http://blog.roberthallam.org/2017/12/solved-logical-volume-is-used-by-another-device/comment-page-1/
Grow physical volume
Assuming your LVM partition is the last one, use fdisk to delete and recreate it, remember to set type to LVM again and reboot. Then use pvresize /dev/sdaX
Or just:
pvresize /dev/sdb
Remove physical drive from a volume group
Make sure the data fits on remaining drives, then
pvmove /dev/sdbX vgreduce vgname /dev/sdbX
Create volume group
vgcreate vgname /dev/sdc1 /dev/sdd1
pvcreate Can't open /dev/sdg exclusively. Mounted filesystem?
Device /dev/sdb excluded by filter
Check disk label(gpt!!
Try:
wipefs -af /dev/sdg
WARNING: Device /dev/dm-17 not initialized in udev database even after waiting 10000000 microseconds.
Try
udevadm trigger
wipefs: error: /dev/sdg: probing initialization failed: Device or resource busy
try all ways to unbusy
Check if volume is in use
dmsetup info -c
Check the 'Open' column
WARNING: PV /dev/sda5 in VG foo-vg is using an old PV header, modify the VG to update.
vgck --updatemetadata foo-vg