How Does Fedora 25 Split Large Filesystems
-
@scottalanmiller Definitely odd. I will try this myself.
-
How would you handle that @scottalanmiller ? Just expand the root , or make extra LVM volumes for things like /home ?
-
@dafyre said in How Does Large Fedora 25 Split Filesystems:
How would you handle that @scottalanmiller ? Just expand the root , or make extra LVM volumes for things like /home ?
That is what centos does
-
@dafyre said in How Does Large Fedora 25 Split Filesystems:
How would you handle that @scottalanmiller ? Just expand the root , or make extra LVM volumes for things like /home ?
Totally depends. I normally don't make a separate /home filesystem unless this is a desktop or a jump box. Normal servers have no need for home directories of any size, or even at all. We might have 1MB of data in all /home directories across all servers that we have total. But one desktop might need several TB of data in there!
Now making something special for /data or /var/data or something like that, yes that would be common.
-
Here is what a Fedora 25 NetInstall system did.
I created a generation 2 Hyper-V VM on Hyper-V Server 2016.
I left the default 127GB VHDX size the Windows uses.
I installed, letting Fedora's installed automatically create all partitioning (same as I do with CentOS 7)
Nothing else done yet.[root@test ~]# df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 435M 0 435M 0% /dev tmpfs 446M 0 446M 0% /dev/shm tmpfs 446M 1.4M 445M 1% /run tmpfs 446M 0 446M 0% /sys/fs/cgroup /dev/mapper/fedora-root 15G 1.7G 14G 11% / /dev/sda2 976M 96M 813M 11% /boot /dev/sda1 200M 9.4M 191M 5% /boot/efi tmpfs 446M 4.0K 446M 1% /tmp tmpfs 90M 0 90M 0% /run/user/0[root@test ~]# pvdisplay --- Physical volume --- PV Name /dev/sda3 VG Name fedora PV Size 125.80 GiB / not usable 2.00 MiB Allocatable yes PE Size 4.00 MiB Total PE 32205 Free PE 27854 Allocated PE 4351 PV UUID gZPmZ3-KbaN-XtkI-uwPY-gxGi-J1gb-Hn3RBV[root@test ~]# vgdisplay --- Volume group --- VG Name fedora System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 3 VG Access read/write VG Status resizable MAX LV 0 Cur LV 2 Open LV 2 Max PV 0 Cur PV 1 Act PV 1 VG Size 125.80 GiB PE Size 4.00 MiB Total PE 32205 Alloc PE / Size 4351 / 17.00 GiB Free PE / Size 27854 / 108.80 GiB VG UUID WLGoMH-tJnA-JM0h-leh6-MPFX-L1NV-RWLAed--- Logical volume --- LV Path /dev/fedora/swap LV Name swap VG Name fedora LV UUID OeJ6qt-1fjy-iRkI-zyqk-iINr-yta0-RquNfO LV Write Access read/write LV Creation host, time test.ad.bundystl.com, 2017-04-20 22:18:31 -0500 LV Status available # open 2 LV Size 2.00 GiB Current LE 511 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:1--- Logical volume --- LV Path /dev/fedora/root LV Name root VG Name fedora LV UUID aKHycu-MmgE-Eu0Q-f7tE-pyIC-cAeS-PRgWp6 LV Write Access read/write LV Creation host, time test.ad.bundystl.com, 2017-04-20 22:18:31 -0500 LV Status available # open 1 LV Size 15.00 GiB Current LE 3840 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0 -
So the answer is that Fedora creates a 15GB partition to install to and a swap disk, then leaves the rest of the space alone to be setup later.
-
@JaredBusch said in How Does Fedora 25 Split Large Filesystems:
So the answer is that Fedora creates a 15GB partition to install to and a swap disk, then leaves the rest of the space alone to be setup later.
Correct, at least that's what it did in my test, which I assume was pretty generic.
-
@scottalanmiller said in How Does Fedora 25 Split Large Filesystems:
@JaredBusch said in How Does Fedora 25 Split Large Filesystems:
So the answer is that Fedora creates a 15GB partition to install to and a swap disk, then leaves the rest of the space alone to be setup later.
Correct, at least that's what it did in my test, which I assume was pretty generic.
Yeah, I was just following up with my own test and a few more posted details. I expected it to match yours. If it hadn't I would be really confused.
-
@JaredBusch So Fedora prefers to not make an assumption about where you want your HD space allocated but CentOS knows you're most likely not going to want more than 50 GB in your root partition? Just making sure I understand the reasoning.
-
I didn't realize Fedora did it like that. I prefer that method most. I'd rather put it where I want after a quick default install, than it put it somewhere I don't want it automatically.
-
@Tim_G said in How Does Fedora 25 Split Large Filesystems:
I didn't realize Fedora did it like that. I prefer that method most. I'd rather put it where I want after a quick default install, than it put it somewhere I don't want it automatically.
Yeah, this is much better than what CentOS does.
-
@Tim_G said in How Does Fedora 25 Split Large Filesystems:
I didn't realize Fedora did it like that. I prefer that method most. I'd rather put it where I want after a quick default install, than it put it somewhere I don't want it automatically.
I agree.
-
I really dislike how CentOS 7 will take a large disk and create a 50GB setup for everything and then a separate partition to everything over 50 and moutn it in /home.
-
@JaredBusch said in How Does Fedora 25 Split Large Filesystems:
I really dislike how CentOS 7 will take a large disk and create a 50GB setup for everything and then a separate partition to everything over 50 and moutn it in /home.
That sounds like they expect that every large install is going to be used for end users to log into. Isn't that pretty unlikely?
-
@Reid-Cooper said in How Does Fedora 25 Split Large Filesystems:
@JaredBusch said in How Does Fedora 25 Split Large Filesystems:
I really dislike how CentOS 7 will take a large disk and create a 50GB setup for everything and then a separate partition to everything over 50 and moutn it in /home.
That sounds like they expect that every large install is going to be used for end users to log into. Isn't that pretty unlikely?
This is what CentOS 7 does by default with a 150GB VHDX.
[root@bna-nc ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/cl-root 50G 1.9G 49G 4% / devtmpfs 439M 0 439M 0% /dev tmpfs 449M 0 449M 0% /dev/shm tmpfs 449M 46M 404M 11% /run tmpfs 449M 0 449M 0% /sys/fs/cgroup /dev/sda2 1014M 174M 841M 18% /boot /dev/sda1 200M 9.5M 191M 5% /boot/efi /dev/mapper/cl-home 97G 6.5G 91G 7% /home tmpfs 90M 0 90M 0% /run/user/0[root@bna-nc ~]# pvdisplay --- Physical volume --- PV Name /dev/sda3 VG Name cl PV Size 148.80 GiB / not usable 2.00 MiB Allocatable yes PE Size 4.00 MiB Total PE 38093 Free PE 1 Allocated PE 38092 PV UUID 5YZ3rY-LPgV-W0Vi-LoOm-5byv-PdwA-iPaJvP[root@bna-nc ~]# vgdisplay --- Volume group --- VG Name cl System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 4 VG Access read/write VG Status resizable MAX LV 0 Cur LV 3 Open LV 3 Max PV 0 Cur PV 1 Act PV 1 VG Size 148.80 GiB PE Size 4.00 MiB Total PE 38093 Alloc PE / Size 38092 / 148.80 GiB Free PE / Size 1 / 4.00 MiB VG UUID fuOf2r-zmeW-gCxG-b8MX-9JQ2-m3RG-S2Y2mh -
@Reid-Cooper said in How Does Fedora 25 Split Large Filesystems:
@JaredBusch said in How Does Fedora 25 Split Large Filesystems:
I really dislike how CentOS 7 will take a large disk and create a 50GB setup for everything and then a separate partition to everything over 50 and moutn it in /home.
That sounds like they expect that every large install is going to be used for end users to log into. Isn't that pretty unlikely?
That's rarely the case now (at least in my recent personal experience)... maybe 10 years ago it was more likely.
-
@Tim_G said in How Does Fedora 25 Split Large Filesystems:
@Reid-Cooper said in How Does Fedora 25 Split Large Filesystems:
@JaredBusch said in How Does Fedora 25 Split Large Filesystems:
I really dislike how CentOS 7 will take a large disk and create a 50GB setup for everything and then a separate partition to everything over 50 and moutn it in /home.
That sounds like they expect that every large install is going to be used for end users to log into. Isn't that pretty unlikely?
That's rarely the case now (at least in my recent personal experience)... maybe 10 years ago it was more likely.
Maybe 20 years ago.
-
I seen that in Fedora 27 NetInstall, it doesn't create a /home partition automatically. It only does the following by default:
I found RedHat's partitioning recommendations, and it recommends a separate /home partition with the follow minimum sizes. Be sure to look at the note below, as I think that's a great way to go about it.
If you assign all extra space to /home, and then later you run out of room in /, then you'll wish you'll had more available.
-
@tim_g said in How Does Fedora 25 Split Large Filesystems:
I seen that in Fedora 27 NetInstall, it doesn't create a /home partition automatically. It only does the following by default:
I found RedHat's partitioning recommendations, and it recommends a separate /home partition with the follow minimum sizes. Be sure to look at the note below, as I think that's a great way to go about it.
If you assign all extra space to /home, and then later you run out of room in /, then you'll wish you'll had more available.
Yeah, splitting off /home comes from another era and what is today a very rare use case that almost never comes up. Reducing space in / so that you don't overfill a directory that is essentially never used is pretty silly.
-
@scottalanmiller said in How Does Fedora 25 Split Large Filesystems:
@tim_g said in How Does Fedora 25 Split Large Filesystems:
I seen that in Fedora 27 NetInstall, it doesn't create a /home partition automatically. It only does the following by default:
I found RedHat's partitioning recommendations, and it recommends a separate /home partition with the follow minimum sizes. Be sure to look at the note below, as I think that's a great way to go about it.
If you assign all extra space to /home, and then later you run out of room in /, then you'll wish you'll had more available.
Yeah, splitting off /home comes from another era and what is today a very rare use case that almost never comes up. Reducing space in / so that you don't overfill a directory that is essentially never used is pretty silly.
I like production data in it's own partition.. whether it's /data or in /home depending on the situation.
