On 05/06/17 03:20 PM, Anton Aylward wrote:
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.
leaving aside the matter of Thin Pools, , leaving aside the issue of file systems who seize cannot be adjusted or can only grow, you seem to miss out on my point about "deferred design".
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.
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. But back in Ancient Of Days this kind of thing was discouraged since in user space a DoS script could do great damage:
while true do mkdir whatever cd whatever done
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.
The ability to use 'lvmove' on a live system and watch the metrics made this work.
Then there was the matter of moving LVs off a dying 'drive'. What? you ask, didn't Anton say this was RAID? Yes, it was RAID for striping - that is !speed! - not RAID for reliability.
Oh, the OS & user space was on a separate subsystem and that was simply mirrored.
You can do a lot of things with LVM beyond simply increasing the size of a LV and the file system on it.
I assign 70GB for my Crucial MX300 525 GB SSD. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org