Am 05.06.2017 um 21:20 schrieb Anton Aylward:
On 05/06/17 12:56 PM, Peter Mc Donough wrote:
No, just wondering whether LVM for a system is really necessary unless you now that system space requirement are really increasing that much over time.
I think you have a dramatic misunderstanding of what LVM is about.
Probably, my system doesn't require it. You mentioned a Laptop with a 90G HDD with LV. Why would you need an LVM there. It can't be data-protection, you would need a second physical drive for it. As for server-OS space, how much, 5GB?, it is very unlikely that it will suddenly grow beyond 10GB. The database or the mail-archive or the /tmp directory may, in this case wouldn't it make more sense to put everything on one big drive and have something like a full disk alert warning. This problem is so old, I could bet that a solution is probably available for free on each Linux. ...
If one is experienced, the one will know pretty well how large (or small) to make a partition. You mention that you expect a RootFS to be be about 10G for a basic install. So why make a partition any bigger? Certainly in the days before terabit drives were under $100 space was more critical.
Having a nearly empty partition, which may some unknown time in future be required is OK, but wasting disk space when I'm fairly certain I will not need is simply uncool.
The BtrFS approach, "One FS to Rule Them All", one FS for no matter how many spindles/media is a solution. Its all one pool, but the subvolumes offer 'management'. really, if one runs BtrFS, then what's the point in having a seperate /home¿ Well, that's one solution.
btfs has its advantages, but I can't see any for my computer usage. It is very unlikely that I would kept the data to roll back Tumbleweed to solve my original problem, the increase on / from 10G to 12G over three month. If necessary, it will be quicker to install a fresh Tumbleweed.
But back in Ancient Of Days this kind of thing was discouraged since in user space a DoS script could do great damage: .... So, yes, partitions with hard boundaries. In a former life I administered a a system with about 150T of database space, RAID_LVM. The spindles were, mostly, 350G. That probably tells you the era :-) The issue here wasn't that LVM could make a file system over multiple "logical" drives, but it was about having a dozen (perhaps, I don't recall) logical database volumes. The volumes needed to be demand-balanced, and that involved moving the LVs to the optimum layout across all the drives.
This gave me the idea that you use LVM because you are used to it and not because it is necessary. Which is absolutely fine. There are simply more interesting ways of spending our lifetime than changing a partition-layout if there is not obvious advantage in it.
... You can do a lot of things with LVM beyond simply increasing the size of a LV and the file system on it.
But do I need it? Have a nice evening. Peter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org