Description of problem: Cryptsetup supports unlocking BitLocker volumes, but there's no support for modifying the metadata. 1. Determine if modifying the BitLocker metadata is necessary to support resize (i.e. is it similar to LUKS which has no explicit size and the dm-crypt volume inherits size from the underlying partition the LUKS header is located on) https://lore.kernel.org/cryptsetup/22b5eb15-eda6-5eef-c504-c92da4fd1aab@gmail.com/T/#t If BitLocker volumes can be safely resized: 2. Anaconda needs to ask the user for a BitLocker Recovery key 3. Anaconda needs to leverage libcryptsetup's BitLocker support, in order to unlock the volume with the user provided BitLocker Recovery key, and to facilitate the resize of the NTFS file system within.
If Anaconda can't resize the volume, then it should at least show a human readable message to explain what the issue is, and point the user in the direction of fixing it. For example, we could recommend that someone resizes the volume in Windows. Ideally we'd also point to documentation explaining how to do this.
(In reply to Chris Murphy from comment #0) > Description of problem: > > Cryptsetup supports unlocking BitLocker volumes, but there's no support for > modifying the metadata. > > 1. Determine if modifying the BitLocker metadata is necessary to support > resize (i.e. is it similar to LUKS which has no explicit size and the > dm-crypt volume inherits size from the underlying partition the LUKS header > is located on) > > https://lore.kernel.org/cryptsetup/22b5eb15-eda6-5eef-c504- > c92da4fd1aab/T/#t I answered on the mailing list, it unfortunately isn't this simple, the volume size is written in the BitLocker FVE metadata so it will be necessary to change the metadata too and that's something we don't want to do in cryptsetup and it's potentially very dangerous because we don't fully understand the metadata. > > If BitLocker volumes can be safely resized: > > 2. Anaconda needs to ask the user for a BitLocker Recovery key > > 3. Anaconda needs to leverage libcryptsetup's BitLocker support, in order to > unlock the volume with the user provided BitLocker Recovery key, and to > facilitate the resize of the NTFS file system within. Speaking as a Blivet maintainer here: We can talk about adding support for resizing BitLocker when there is a tool or library that supports it, we definitely won't be doing this in Blivet. Currently the safest (and probably the only) way is for the user to resize the volume from Windows. I understand this is a problem, I saw the question on askfedora too and I agree we'll see more in the future, but this needs to be fixed somewhere else first. I'll keep this RFE open for the future.
(In reply to Allan Day from comment #1) > If Anaconda can't resize the volume, then it should at least show a human > readable message to explain what the issue is, and point the user in the > direction of fixing it. For example, we could recommend that someone resizes > the volume in Windows. Ideally we'd also point to documentation explaining > how to do this. We are unfortunately not doing a good job when informing the user why a device/format is not resizable. Blivet doesn't have a simple API to tell you the reason and Anaconda doesn't have a way to show this information in the UI. We have a similar bug where NTFS is not resizable because it contains a suspended system and we also don't have a way to convey this. But this is a separate issue and more for Anaconda than Blivet. Can you please report this against Anaconda?
I think the best option in the short term is to document how to use the Windows "Disk Management" tool to resize the volume from within Windows. That way Anaconda has free space to install into, and an automatic installation just works.
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.