iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
LVM lets you pool one or more VPS disks into a volume group, carve out logical volumes, and expand storage without redesigning your filesystem layout. The safe workflow is layered: confirm that your VPS provider has exposed a usable block device, initialize it as a physical volume (PV), add it to a volume group (VG), create a logical volume (LV), format and mount it, then grow each layer in order when capacity increases. LVM snapshots can support backup workflows, but they require free space and are not independent backups.
What LVM does on a VPS
Logical Volume Management is a storage abstraction that sits between block devices and filesystems. Instead of formatting an entire disk and accepting its fixed partition boundaries, you create a pool of capacity and allocate virtual block devices from that pool. Canonical describes LVM as a method of allocating and managing storage that is more advanced and flexible than traditional partitioning.
LVM cannot create capacity that the VPS provider has not supplied. Your provider must expose an additional block device or let you enlarge an existing virtual disk. Only then can the Linux guest use LVM to organize the new space.
The three LVM layers
| Layer | What it represents | Typical commands | What normally happens next |
|---|---|---|---|
| Physical volume (PV) | A whole disk or partition initialized for LVM metadata. | pvcreate, pvs, pvdisplay |
The PV contributes capacity to a volume group. |
| Volume group (VG) | A storage pool made from one or more PVs. | vgcreate, vgextend, vgs, vgdisplay |
Free extents in the pool are assigned to logical volumes. |
| Logical volume (LV) | A virtual block device allocated from a VG. | lvcreate, lvextend, lvs, lvdisplay |
You put a filesystem on the LV, then mount it. |
The filesystem is not an LVM layer. It occupies the LV and has its own rules for growing or shrinking. Increasing an LV does not automatically make the filesystem use the new blocks.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
Why use LVM on a VPS?
- Flexible allocation: create several LVs from one pool and leave unallocated space available for later.
- Online growth: many filesystems can be grown while mounted after the underlying LV is extended.
- Multiple disks in one pool: add another PV to an existing VG instead of moving data to a new mount point.
- Storage-specific LV types:
lvcreatesupports linear, striped, mirrored, snapshot, and thin-pool layouts, subject to the performance and redundancy characteristics of the underlying VPS storage. - Point-in-time copies: classic snapshots can present a frozen view of an LV while the original continues serving data.
The trade-off is operational complexity. You must identify the correct device, track free space in both the VG and any snapshots, and remember to grow the filesystem after growing the LV.
Requirements and safety checks
Before changing storage, confirm all of the following:
Free tools Windows power users keep installed
One-click scans. No signup required.
- Your VPS plan exposes a second block device or supports expansion of the existing virtual disk.
- You have console or SSH access with
sudoprivileges. - You know whether the device is a whole disk such as
/dev/sdbor a partition such as/dev/sdb1. - You have a tested backup of important data. Storage commands aimed at the wrong device can destroy an existing filesystem.
- You know the filesystem you intend to use, because ext4 and XFS use different growth commands.
- You have enough free space in the VG for the LV or snapshot you intend to create.
Do not assume that /dev/sdb is unused. Device names can change after reboots, detachments, or provider operations. Always inspect the guest’s current view immediately before running a destructive command.
Inspect the VPS before creating anything
Start with a read-only inventory:
lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINTSLook for the disk or partition supplied by the provider, its size, whether it already has a filesystem, and whether it is mounted. Existing LVM devices normally appear beneath a device-mapper path and can be inspected with:
sudo pvs
sudo vgs
sudo lvsUse blkid when you need filesystem or UUID information:
sudo blkidIf the provider has just attached or enlarged a disk and Linux does not show the new size, resolve that guest-side visibility issue before touching LVM. LVM only operates on the block-device size reported by the kernel.
Create a new LVM data volume
The following example uses a new device named /dev/sdX, a volume group named vg_data, a 100-GiB logical volume named lv_data, and an ext4 filesystem mounted at /srv/data. Replace /dev/sdX with the exact unused device shown by lsblk. In LVM command input, G denotes GiB and M denotes MiB.
1. Back up and verify the target
Make or verify a backup, then run the inventory command again. If the target contains a filesystem, a mount point, or data you cannot discard, stop. The next step writes LVM metadata to the selected device.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
2. Initialize the physical volume
sudo pvcreate /dev/sdXConfirm the result:
sudo pvs
sudo pvdisplay /dev/sdXA PV can be a whole disk or a partition. Use the form that matches the device you deliberately selected.
3. Create or extend a volume group
For a new pool containing this PV:
sudo vgcreate vg_data /dev/sdXFor an existing pool, add the PV instead:
sudo vgextend existing_vg /dev/sdXCheck the pool’s total and free capacity:
sudo vgs
sudo vgdisplay vg_data4. Allocate a logical volume
sudo lvcreate -L 100G -n lv_data vg_dataThis reserves 100 GiB from vg_data. You can reserve all currently free extents with:
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →sudo lvcreate -l 100%FREE -n lv_data vg_dataUse 100%FREE only after deciding that the VG should have no reserve for future LVs, snapshots, or emergency growth. Verify the mapping:
sudo lvs
sudo lvdisplay /dev/vg_data/lv_data5. Create the filesystem
Formatting destroys any data on the LV. For ext4:
sudo mkfs.ext4 /dev/vg_data/lv_dataIf you choose XFS instead, use the distribution’s XFS formatter and remember that XFS grows online but cannot be shrunk in place. Do not run an ext4 growth tool against an XFS filesystem or vice versa.
6. Mount the LV
sudo mkdir -p /srv/data
sudo mount /dev/vg_data/lv_data /srv/dataValidate the active mount and filesystem type:
findmnt /srv/data
lsblk -f
df -hT /srv/data7. Persist the mount with a UUID
Device names are less stable than filesystem UUIDs. Obtain the UUID:
sudo blkid /dev/vg_data/lv_dataAdd a line to /etc/fstab using the UUID printed by that command. A shell-generated entry avoids mistyping the value:
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsUUID=$(sudo blkid -s UUID -o value /dev/vg_data/lv_data)
printf 'UUID=%s /srv/data ext4 defaults,nofail 0 2n' "$UUID" | sudo tee -a /etc/fstabFor an XFS filesystem, replace ext4 in the entry with xfs. Test the file before rebooting:
sudo mount -a
findmnt /srv/dataIf mount -a reports an error, fix the entry while the current mount is still available. A malformed fstab line can prevent a normal boot or leave the data volume unavailable.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Add a second VPS disk to an existing LVM pool
Attaching a separate block device is usually the least ambiguous expansion path. After the provider attaches the disk, confirm its name and size with lsblk. Then perform the PV and VG steps:
- Verify that the new device has no required data and is not mounted.
- Initialize it:
sudo pvcreate /dev/sdY. - Add it to the pool:
sudo vgextend vg_data /dev/sdY. - Check the new free capacity:
sudo vgs. - Extend an existing LV or create another LV, depending on your allocation plan.
For example, to add 20 GiB to the existing data LV:
sudo lvextend -L +20G /dev/vg_data/lv_dataThe new disk may have different performance or failure characteristics from the original. A linear LV can place extents across both PVs, so losing one underlying device can affect the LV. LVM allocation is not, by itself, redundancy or a backup.
Expand an LVM volume after increasing the VPS disk
Expansion has separate provider, partition, PV, VG, LV, and filesystem stages. Complete only the stages that apply to your layout.
1. Increase capacity at the provider
Use the VPS control panel or provider API to enlarge the virtual disk, or attach another block device. The guest cannot use capacity that the provider has not exposed.
2. Confirm the new size in Linux
lsblkIf the disk size is larger but the LVM PV is on a partition that still ends at the old boundary, the partition must be extended first with the partitioning tool appropriate to your distribution and partition table. Do not recreate the partition or alter its starting sector.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall3. Resize the PV
For a PV on an expanded partition:
sudo pvresize /dev/<partition>For a PV that occupies the whole expanded disk, use that disk path instead. Confirm that the VG has gained free extents:
sudo pvs
sudo vgs4. Extend the LV
Extend by a defined amount:
sudo lvextend -L +20G /dev/vg_data/lv_dataOr assign all currently free VG space:
sudo lvextend -l +100%FREE /dev/vg_data/lv_dataUse the lowercase -l form for extents and uppercase -L for a size. Check the LV size before growing the filesystem:
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
sudo lvs5. Grow the filesystem
For ext4, run:
sudo resize2fs /dev/vg_data/lv_dataFor XFS, provide the mounted path:
sudo xfs_growfs /srv/dataSome LVM versions support a combined request:
sudo lvextend -r -L +20G /dev/vg_data/lv_dataThe -r option asks the system to resize the filesystem as well. Verify the actual result rather than assuming it succeeded:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
sudo lvs
df -hT /srv/dataDo not attempt to shrink a mounted filesystem as part of this procedure. Filesystem shrinking has filesystem-specific prerequisites and is riskier than online growth.
Use LVM snapshots for backup workflows
A classic LVM snapshot records the original LV’s state at the instant the snapshot is created. The original LV remains usable, while the snapshot presents a point-in-time image. This can let a backup program read a consistent filesystem view without stopping the running service.
Create and mount a snapshot
sudo lvcreate -s -L 10G -n lv_data_snap /dev/vg_data/lv_dataThe -L 10G value is snapshot copy-on-write space, not the size of the source LV. Mounting a snapshot read-only is a prudent default:
sudo mkdir -p /mnt/data-snapshot
sudo mount -o ro /dev/vg_data/lv_data_snap /mnt/data-snapshotRun the backup from /mnt/data-snapshot, then unmount and remove the snapshot when the backup is complete:
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →sudo umount /mnt/data-snapshot
sudo lvremove /dev/vg_data/lv_data_snapMonitor snapshot consumption
sudo lvsAs blocks on the original LV change, LVM stores the old versions in the snapshot’s allocated area. If that area fills, the snapshot becomes unusable. Size the snapshot for the expected write rate and backup duration, and monitor it while the backup runs.
Understand the backup boundary
A snapshot is stored in the same LVM storage system as its source unless you copy its contents elsewhere. Losing the VPS disk, the VG, or the underlying provider volume can therefore lose both the source and snapshot. Copy backup data to independent storage and test restoring it. A snapshot also provides filesystem-level consistency, not automatic application-level consistency; databases and other write-heavy services may need a flush, checkpoint, or brief quiesce procedure.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choose between LVM, a provider volume, and filesystem-native storage
The best layer depends on who should manage capacity, snapshots, and recovery.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
| Option | Online expansion | Snapshot behavior | Portability between VPS hosts | Performance and redundancy | Operational recovery |
|---|---|---|---|---|---|
| LVM logical volume | Usually straightforward when the provider disk, PV, VG, LV, and filesystem are expanded in sequence. | Classic LVM snapshots are available; snapshot space must be monitored and copied elsewhere for an independent backup. | Requires moving or reassembling the PV/VG/LV structure and matching filesystem support. | Flexible allocation and multiple LV types, but allocation across PVs does not automatically provide redundancy. | Requires knowledge of LVM metadata, filesystem tools, and mount configuration. |
| Provider-attached block volume | Depends on the provider’s resize workflow and the guest’s partition, PV, LV, and filesystem layout. | Provider snapshots may be simpler to schedule, but their consistency and restore behavior are provider-specific. | Often tied to the provider’s region, account, or volume system. | Performance, replication, and failure handling are defined by the provider’s service. | Provider controls can simplify reattachment, while guest configuration still needs to be restored. |
| Filesystem-native volume or direct filesystem on a disk | Uses the filesystem and partition tools directly; there is no VG allocation layer. | Uses filesystem-native or provider mechanisms rather than LVM snapshots. | Usually easier to understand on another Linux host, subject to filesystem support. | Fewer abstraction layers, but no LVM pooling or LV allocation types. | Fewer LVM steps, but less flexibility when adding multiple devices. |
Choose LVM when you value pooled capacity, multiple independently mounted volumes, and controlled online growth. A provider-managed volume or filesystem-native design may be simpler when the provider already supplies the snapshot, replication, and resize operations you need.
Recommended Free Tools
Common failure modes and fixes
The new disk does not appear
Check the provider attachment or resize operation, then run lsblk and inspect kernel storage messages using your distribution’s normal logging tools. Do not run pvcreate until the intended device is visible and identified.
pvcreate warns about an existing filesystem
Stop and verify the device. The warning may indicate real data. Only overwrite it after confirming that the device is disposable and that a backup exists.
The VG has no free space
Run vgs and pvs. If the provider disk was enlarged, the partition and PV may still have their old sizes. If a separate disk was attached, it may not yet have been initialized and added with vgextend.
The LV grew but df -hT did not
The filesystem is a separate layer. Identify its type with lsblk -f or df -hT, then use resize2fs for ext4 or xfs_growfs for XFS. Recheck both lvs and df -hT.
The mount fails after reboot
Check the UUID and filesystem type in /etc/fstab, then run sudo mount -a and inspect findmnt. Ensure the VG and LV are activated by the distribution’s normal boot services and that the mount-point directory exists.
A snapshot becomes invalid
Run sudo lvs to inspect snapshot usage. A full classic snapshot cannot continue tracking changed blocks. Remove it, recreate one with an appropriately sized allocation, and shorten the backup window or reduce the source write rate.
Quick Recap
Operating LVM safely over time
- Record the intended PV, VG, LV, filesystem, and mount point for every volume.
- Keep free extents in the VG when you expect future snapshots or emergency growth.
- Monitor
vgs,lvs, and filesystem free space; they measure different resources. - Use UUIDs in
/etc/fstaband validate changes withmount -abefore rebooting. - Keep provider-level backups or copies on independent storage; LVM metadata and snapshots do not protect against loss of the underlying VPS.
- Test restoring a backup on a separate instance so that the recovery sequence is known before an outage.
- Document whether each PV is a whole disk or partition, especially after provider resize operations.
End-to-end command checklist
- Inspect:
lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINTS. - Back up important data.
- Create or confirm the PV:
sudo pvcreate /dev/sdX. - Create or extend the VG:
sudo vgcreate vg_data /dev/sdXorsudo vgextend vg_data /dev/sdX. - Create the LV:
sudo lvcreate -L 100G -n lv_data vg_data. - Format it with the chosen filesystem.
- Mount it and verify with
findmnt,lsblk -f, anddf -hT. - Persist the mount by UUID and test with
sudo mount -a. - For expansion, grow the provider disk or attach a disk, extend a partition if needed, run
pvresize, extend the VG and LV, then grow the filesystem. - For snapshots, allocate copy-on-write space, monitor
lvs, copy data to independent storage, and remove the snapshot when finished.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
