On 2024-08-04 21:16, David Uhden Collado wrote: > Hello, > I have observed that the automatic partitioning feature of disklabel(8) > does not allocate more than approximately 350GB to system partitions > [1]. In my opinion, the tool should have been designed to use all > available space on the storage device when partitioning. To address this > limitation, I had to write a custom program that calculates partition > sizes to maintain their initial proportions while occupying the entire > storage device. > I would like to understand the rationale behind this design choice. Is > there a specific reason why the automatic partitioning is limited to > around 350GB for system partitions? Any insights or explanations you can > provide would be greatly appreciated.
There is at least one quite prevalent problem with using Really Large filesystems that is a good reason for this: when you need to boot a system that wasn't shut down orderly enough that all filesystems got properly unmounted, the amount of time it takes for the fsck (file system repair tool) that is automatically triggered at the next reboot to finish will be a nuisance long before it completes. A few other, possibly less convincing reasons to cap the sizes of filesystems is backups and restores get cumbersome, solving problems where you need to grow a partition is far easier if you have unused disk space, and solid state disk reliability improves when a decent fraction of available storage is unused. MfG, -- Åke Nordin <ake.nor...@netia.se>, resident Net/Lunix/telecom geek. Netia Data AB, Stockholm SWEDEN *46#7O466OI99#
