From Fedora Project Wiki

No edit summary
(mention /boot(/efi), simplify and clarify subvolumes instructions)
Line 8: Line 8:
# Select a Fedora {{FedoraVersionNumber|next}} installer for any Edition or Spin which uses ''Btrfs'' filesystem by default.
# Select a Fedora {{FedoraVersionNumber|next}} installer for any Edition or Spin which uses ''Btrfs'' filesystem by default.
{{Template:partitioning_actions}}
{{Template:partitioning_actions}}
# In Installation Destination, click ''Advanced Custom (Blivet-GUI)'' under Storage Configuration
# In Installation Destination, use ''Advanced Custom (Blivet-GUI)'' partitioning
# Under ''Btrfs Volumes'', locate the previous Fedora installation, click on it to reveal existing mount points for reuse
# On the disk drive containing the existing Fedora installation, make sure the existing partitions formerly used as `/boot` and `/boot/efi` (if applicable) are reformatted and the same mountpoints are again assigned to them. (Alternatively, you can create new partitions and leave the old ones intact and without mountpoints).
# Select appropriate mount point looks like `/var/lib/machines`, right click and delete it.
# In the list of existing btrfs volumes, locate the `home` subvolume of the existing installation and set the `/home` mountpoint to it.
# Select `home` mount point, right click, Click ''Edit'' and find '''Set Mountpoint''' field, type in `/home`, click ''Set Mountpoint'' button.
# You can delete all the other btrfs subvolumes, or you can keep them intact, but without any mountpoints assigned.
# Click {{key|+}} button to create a new `/` mount point (NOTE: this is required to be a new subvolume. Optional: change the name of the subvolume from `root` to `rootkde` or `rootjam` per your preference).. Click ''OK'' button.
#* This refers to the `root` subvolume, but you can also see some additional subvolumes present as well, like `root/var/lib/machines` or `root/var/lib/portables`.
#* Note: If you don't delete the previous `root` subvolume, the installer will create a new subvolume `root00` mounted at `/`. If you delete the previous `root` subvolume first, the installer will use the same `root` name for the new one. Both approaches are valid, you can use whichever approach you choose. Other than consuming space, there is no disadvantage to keeping the old `root`.
# Create a new `root` subvolume and set the `/` mountpoint to it.
# Click ''Done''
#* If you already have a `root` subvolume, because you decided to not delete the old one, that's not a problem, just name the new one differently.
# Perform the installation and reboot the machine. At the initial setup, it's recommended to use all the same settings as for the 1st installation.
# Perform the installation and reboot the machine. At the initial setup, it's recommended to use all the same settings as for the first installation.
# After logging in, check that your home directory or `/home` contains the files you created on your previous system (check their contents as well)
# After logging in, check that your home directory or `/home` contains the files you created on your previous system (check their contents as well).
|results=
|results=
{{Template:partitioning_results}}
{{Template:partitioning_results}}
# Your personal files on your `/home` partition must be intact
# The partitions and subvolumes which were assigned some mountpoints in the installer should be mounted, and the partitions and subvolumes which weren't assigned any mountpoints shouldn't be mounted.
# Your personal files on your `/home` partition must be intact.
}}
}}
[[Category:Installer_Partitioning_Test_Cases]]
[[Category:Installer_Partitioning_Test_Cases]]
[[Category:btrfs]]
[[Category:btrfs]]

Revision as of 15:42, 7 December 2020

Note.png
Associated release criterion
This test case is associated with the Fedora_40_Beta_Release_Criteria#Custom_partitioning release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.

Description

This test case ensures that the data in the /home directory is retained and usable on a Btrfs layout after another Fedora is installed on the same partition.

Setup

  1. Install Fedora 39 or 40 from any Edition or Spin which uses Btrfs filesystem by default. Use Automatic storage configuration during disk partitioning.
  2. On the installed system, create some distinct files and directories in your home directory or directly in /home

How to test

  1. Select a Fedora 40 installer for any Edition or Spin which uses Btrfs filesystem by default.
  2. Boot the GTK-based installer using any available means. Do not use Fedora Workstation live on Fedora 41+, as that uses the webui-based installer.
  3. Proceed to the installer's main screen, making sensible choices, and enter the Installation Destination screen.
  4. In Installation Destination, use Advanced Custom (Blivet-GUI) partitioning
  5. On the disk drive containing the existing Fedora installation, make sure the existing partitions formerly used as /boot and /boot/efi (if applicable) are reformatted and the same mountpoints are again assigned to them. (Alternatively, you can create new partitions and leave the old ones intact and without mountpoints).
  6. In the list of existing btrfs volumes, locate the home subvolume of the existing installation and set the /home mountpoint to it.
  7. You can delete all the other btrfs subvolumes, or you can keep them intact, but without any mountpoints assigned.
    • This refers to the root subvolume, but you can also see some additional subvolumes present as well, like root/var/lib/machines or root/var/lib/portables.
  8. Create a new root subvolume and set the / mountpoint to it.
    • If you already have a root subvolume, because you decided to not delete the old one, that's not a problem, just name the new one differently.
  9. Perform the installation and reboot the machine. At the initial setup, it's recommended to use all the same settings as for the first installation.
  10. After logging in, check that your home directory or /home contains the files you created on your previous system (check their contents as well).

Expected Results

  1. The expected partition layout should be created on the target device(s).
  2. The install process should complete successfully and the installed system should boot as expected.
  3. The partitions and subvolumes which were assigned some mountpoints in the installer should be mounted, and the partitions and subvolumes which weren't assigned any mountpoints shouldn't be mounted.
  4. Your personal files on your /home partition must be intact.