On Mon, Aug 24, 2020 at 1:15 PM Chris Murphy <lists(a)colorremedies.com> wrote:
On Mon, Aug 24, 2020 at 1:12 PM Chris Murphy <lists(a)colorremedies.com> wrote:
>
> On Mon, Aug 24, 2020 at 4:40 AM Alessio <alciregi(a)posteo.net> wrote:
> >
> > Hello.
> > I was performing some random test of F33.
> > There is a thing that I can't understand.
> > If I reinstall the system on an disk where I already installed Fedora
> > 33 before, and I want to preserve the content of the home subvolume, is
> > this feasible? I tried various things using Anaconda, but I'm still not
> > able to figure out how to achieve this task.
>
> It is possible.
>
> Using Custom partitioning UI, I suggest in order:
>
> 1. Create /boot/efi or BIOS Boot mount point (can be reused or reformatted)
> 2. Create /boot mount point (can be reused or reformatted)
> 3. Create / mount point (this is required to be a new subvolume)
> 4. Locate the home subvolume you want, the current UI it's pretty easy
> to find if there are no snapshots; if there are many snapshots, you'll
> have to look around for it.
> 5. Click on that subvolume, and on the right hand side at the top,
> find Mount Point field; type in /home; click Update Settings button.
> 6. Click Done
>
> This is a rough draft :) I'm going by memory.
In fact, we should probably make this a Test Case. And discuss making
it a release blocking criterion, as it's a significant feature. We've
always had this capability with LVM+ext4 because /home was a separate
file system that you can just reuse. And the steps are pretty much the
same for it as for Btrfs.
Final release criteria probably adequately covers it:
"The installer must be able to create and install to any workable
partition layout using any file system and/or container format
combination offered in a default installer configuration."
Beta release criteria is a bit of a gray area but is fudgable:
"Custom partitioning
When using both the installer-native and the blivet-gui-based custom
partitioning flow, the installer must be able to:
- Assign mount points to existing storage volumes"
Is a Btrfs subvolume a "storage volume"? I know what's meant by that,
because there's only one way it can work right now in Custom
partitioning with Btrfs, and that's if this is a reference to
subvolumes.
However, we can't always consider subvolumes to be storage volumes.
For example, the encryption requirement in this same section:
- Encrypt newly-created storage volumes
If you are reusing a 'home' subvolume for /home, on a non-encrypted
Btrfs, there's no way to encrypt any newly created subvolume on that
same Btrfs file system. Here's another one:
- Assign sizes to newly-created storage volumes and containers
Subvolumes don't have size.
- Remove existing storage volumes
Subvolumes can be deleted in Custom and Advanced Custom.
Anyway, it might be OK to just insert "(or subvolumes)" or
"/subvolumes" everywhere it applies.
--
Chris Murphy