Description of problem: I configured LVM using BLIVET. All partitions are XFS. At the begining of the installation step (creating storage) I have an error with "partition vg0-data cannot be smaller than 16 Mio", when I actually set 87Gio (done it twice!). / = 10Gio /opt = 5Gio /tmp = 5Gio /home = 20Gio /usr = 10Gio /var = 5Gio /var/lib = 65Gio /var/log = 2Gio /var/log/audit = 2Gio /var/tmp = 5Gio /data = All remaining space, minus 500 Mio that stays free on the disk Version-Release number of selected component: anaconda-36.16.5 The following was filed automatically by anaconda: anaconda 36.16.5 exception report Traceback (most recent call first): File "/usr/lib/python3.10/site-packages/dasbus/client/handler.py", line 497, in _handle_method_error raise exception from None File "/usr/lib/python3.10/site-packages/dasbus/client/handler.py", line 477, in _get_method_reply return self._handle_method_error(error) File "/usr/lib/python3.10/site-packages/dasbus/client/handler.py", line 444, in _call_method return self._get_method_reply( File "/usr/lib64/python3.10/site-packages/pyanaconda/modules/common/task/__init__.py", line 44, in sync_run_task task_proxy.Finish() File "/usr/lib64/python3.10/site-packages/pyanaconda/installation_tasks.py", line 527, in run_task sync_run_task(self._task_proxy) File "/usr/lib64/python3.10/site-packages/pyanaconda/installation_tasks.py", line 496, in start self.run_task() File "/usr/lib64/python3.10/site-packages/pyanaconda/installation_tasks.py", line 311, in start item.start() File "/usr/lib64/python3.10/site-packages/pyanaconda/installation_tasks.py", line 311, in start item.start() File "/usr/lib64/python3.10/site-packages/pyanaconda/installation_tasks.py", line 311, in start item.start() File "/usr/lib64/python3.10/site-packages/pyanaconda/installation.py", line 400, in run_installation queue.start() File "/usr/lib64/python3.10/threading.py", line 946, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.10/site-packages/pyanaconda/threading.py", line 275, in run threading.Thread.run(self) pyanaconda.modules.common.errors.installation.StorageInstallationError: ('device cannot be smaller than 16 Mio', 'vg0-data') Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz inst.repo=hd:LABEL=FEDORA-S-DV quiet executable: /sbin/anaconda hashmarkername: anaconda hawkey.log: 2022-09-23T13:15:48+0000 INFO === Started libdnf-0.66.0 === kernel: 5.17.5-300.fc36.x86_64 product: Fedora release: Fedora release 36 (Thirty Six) type: anaconda version: 36
Created attachment 1913751 [details] File: anaconda-tb
Created attachment 1913752 [details] File: anaconda.log
Created attachment 1913753 [details] File: dbus.log
Created attachment 1913754 [details] File: dnf.librepo.log
Created attachment 1913755 [details] File: environ
Created attachment 1913756 [details] File: lorax-packages.log
Created attachment 1913757 [details] File: lsblk_output
Created attachment 1913758 [details] File: lvm.log
Created attachment 1913759 [details] File: nmcli_dev_list
Created attachment 1913760 [details] File: os_info
Created attachment 1913761 [details] File: program.log
Created attachment 1913762 [details] File: storage.log
Created attachment 1913763 [details] File: syslog
Created attachment 1913764 [details] File: packaging.log
I wonder if it is not caused by the label name that was too long. I tried a 3d time to partition using LVM and BLIVET, but this time I did not use the same name for `/var/log/audit` partition. Instead of "var_log_audit" (13 chars), I used "log_audit" (9 chars). That is the only changes I made (with no free space at the end also). And as far as I remember, I may had the same issue when paritionning LVM with the CLI few month ago. Can you check if what I say is true, and maybe add a test in BLIVET in order to avoid users like me to use too long label names? Thanks!
The issue could be caused by blivet-gui. Reassigning for further investigation.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.