Hacker News new | past | comments | ask | show | jobs | submit login

lvm requires unallocated space in the volume which makes it kind of garbage to use for snapshots



Personally I've never found this to be issue, as I increase volume sizes base on need, not allocate 100% from the get-go. The space needed for short-lived snapshots is not that big, though that of course can depend on the system.

This also helps dealing with run-away (or long running) processes eating disk space, as you always have some extra space set aside..


Only a little (as much as data will change during the backup). And default filesystems nowadays support resizing downwards so you can make space after initial partitioning.


You have to know in advance to not allocate 100% to root and home otherwise you are SOL when you want to make space later. If you're lucky you can disable swap and temporarily use its allocation to do it, providing that is large enough for the changes.


This is not the case, as like I said you can shrink either of those filesystems and its container and use the freed space for this.

(Also I think lvm doesn't need the volume blocks to be contiguous on the physical volume. So you might have N free space after volume a and M after volume b, and lvm would let you create a new N+M sized volume.)


So when I have root and home mounted because I am using the computer can I shrink them? No because they are mounted.


The easiest way to resize the root partition is probably to boot from eg Ubuntu live/install USB stick. The home partition you can unmount (but not while non root user sessions are using it).


> reboot into another OS

As I said: garbage for snapshots


You need to do it only once (if you didn't do it at install time), not every snapshot.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: