Ask Your Question
1

fedora 30 beta server install partitioning

asked 2019-04-08 12:56:20 -0600

tigerpaws gravatar image

updated 2019-04-08 13:29:15 -0600

I've installed the Fedora 30 server beta several times now, in different circumstances, and each time, the install only defined 15G for the root from the disk being installed to. I used the iso Fedora-Server-dvd-x86_64-30_Beta-1.8.iso. The LVM group has the entire disk (once, a 32G usb key, once a 500G nvme drive), but only swap and root logical volumes are defined. The rest of the space is marked free in the group:

[root@polly ~]# pvscan
  PV /dev/nvme0n1p3   VG fedora_polly    lvm2 [464.56 GiB / 433.85 GiB free]
  Total: 1 [464.56 GiB] / in use: 1 [464.56 GiB] / in no VG: 0 [0   ]

[root@polly ~]# lvscan
  ACTIVE            '/dev/fedora_polly/swap' [15.71 GiB] inherit
  ACTIVE            '/dev/fedora_polly/root' [15.00 GiB] inherit

Now, yes I can extend root, and yes I can generate another lvm, but I have never seen this before, so I'm wondering, is this a bug, or is it done deliberately, and if so, what is the purpose, and what am I expected to do with the free space? Does anyone have any idea why this would happen?

The nvme disk had previously been formatted with a single lvm partition. When I installed, I told the installer to reclaim all the space, and allowed it to auto-configure.

I installed fedora30 workstation in a vm with virt-manager and a 50Gb disk, and the install used the whole disk, so it did not exhibit the same phenomenon.

But, the install of a server in a virtual machine with the same size (50Gb) disk, the same thing happened:

[root@polly-tmp ~]# pvscan
  PV /dev/vda2   VG fedora          lvm2 [<49.00 GiB / <31.93 GiB free]
  Total: 1 [<49.00 GiB] / in use: 1 [<49.00 GiB] / in no VG: 0 [0   ]

[root@polly-tmp ~]# lvscan
  ACTIVE            '/dev/fedora/swap' [2.07 GiB] inherit
  ACTIVE            '/dev/fedora/root' [15.00 GiB] inherit
edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted
1

answered 2019-04-08 22:47:30 -0600

updated 2019-04-08 23:07:57 -0600

This problem was also raised in F29. However, it seems that it does not change policy form. I agree with the question, I raised the issue at F29, and I am concerned about the issue.

 https://ask.fedoraproject.org/en/question/130427/fedora-install-hard-partition-status-15gb-root-limitation-in-auto-select/

Therefore, it is necessary to set partition through manual setting rather than automatic partition setting, and in case of automatic setting, there is need to fix for extend lvm volume as an additional setting.

If you want to expand the root lvm volume without reinstalling, please refer to related information and solve the problem.

https://ask.fedoraproject.org/en/question/134329/resize-root-folder/#134354

C. Root Partition for extend for 50GiB
# lvextend -L  [desire Capacity] /dev/fedora/root -r   
or # lvextend -l 100%FREE /dev/fedora/root -r   

# lvextend -L 50GB /dev/fedora/root -r

I have also notified the F30 developers of the problem that occurred in F29 after installing the F30 trial, and I think that the problem will be fixed.

edit flag offensive delete link more

Comments

Thanks, simmon. So it is clearly a bug, not a policy decision. I wonder, though, why it only appears in the server install, and not the workstation. I never noticed, because in the past, I've always upgraded via dnf instead of re-installing. Did you report this as a bug? I think I will do that just to be sure.

tigerpaws gravatar imagetigerpaws ( 2019-04-09 07:55:34 -0600 )edit

@tigerpaws Have a nice day. I'd already report that problem. I hope to fix it. I'll already use server edition and F29 server is a stable run in my server.

simmon gravatar imagesimmon ( 2019-04-09 08:08:49 -0600 )edit
0

answered 2019-04-09 08:15:00 -0600

tigerpaws gravatar image

After looking at bugzilla to see whether I should report it there, I found that it was already flagged, but as a documentation bug. See https://bugzilla.redhat.com/show_bug.cgi?id=1395157. This is, after all, clearly a policy decision and not documented anywhere. You can see tha actual proposal here: link text. However, even after reading the discussion in the fedora meeting attached to the proposal, I fail to see the exact reasoning. Nevertheless, this should be clearly documented.

I will now flag it with Fedora QA as a documentation issue. Leaving the rest of the disk unpartitioned (via lvm) without saying anything is just stupid.

edit flag offensive delete link more

Comments

I know..thanks re-answer. and this error and another problem write question. and i send mail to f30 developer kevin. I want to see the problem solve and fix to show Fedroa ASAP. I believe that Fedora, which is made up of a lot of dedicated people, will solve these small flaws nicely. And I think that we will be solved by publicizing this problem. It is also a good idea to solve the problem more easily by participating in our own activities.

simmon gravatar imagesimmon ( 2019-04-09 08:37:39 -0600 )edit

Question Tools

1 follower

Stats

Asked: 2019-04-08 12:56:20 -0600

Seen: 89 times

Last updated: Apr 09 '19