Description of problem:
Setting up two different btrfs volumes for two internal disks on a laptop, shows both as having the same size of the first volume's disk.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Have a laptop with two disks (typically SDD+HDD).
2. Go to custom partitioning, and click on automatic partitioning with btrfs (which creates one volume across both disks with two mount points, / and /home )
3. Deselect one of the the disks for the single volume, and create another volume with the other disk. Assign one volume for / and the other for /home .
Both mounts show as having the same space as the first volume's disk (in this case the SSD's size)
Each mount should show the space of their respective disk
Please see the screenshots at https://ask.fedoraproject.org/t/fedora-33-separate-btrfs-partitions-on-ssd-and-hdd/9902 from another user with the same problem as me.
At this time I don't know what the final state of the installated sizes are, as I never went through the install. The "questioner" at that link seems willing to test it, will update bug report with result.
According to the ask.fedoraproject.org link, removing the problematic mountpoint (/home) and creating it again, assigning it to the correct btrfs volume and manually sizing it fixes the problem.
Yep, and the related (original) issue of what Automatic partitioning does, or should do, when two drives are selected is a valid question. What's the expectation? I'd say for sure if the performance of the two drives is very different, then they shouldn't be combined in a single Btrfs volume. (The same thing happened with LVM+ext4 as the Automatic partitioning default.) Maybe it should put boot and sysroot on SSD, and /home on HDD.
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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
Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 33 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, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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 please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.