Red Hat Bugzilla – Bug 533350
Resizing encrypted devices is unsupported
Last modified: 2018-04-05 19:55:04 EDT
Created attachment 367805 [details]
Description of problem:
I have two partitions:
200MB /dev/vda1 as /boot, unencrypted
8GB /dev/vda2 as /, encrypted with dm-crypt and LUKS
Selecting "Shrink current system" in partitioning dialog allows me to shrink only the 200MB partition, not the 8GB one. I have provided a password to the encrypted partition at the start of the install, so it should be accessible.
Using "Custom layout" also does not allow me to resize my encrypted partition, I can't change the predefined number 0.
Version-Release number of selected component (if applicable):
Created attachment 367806 [details]
trying to shrink partition
Created attachment 367807 [details]
using custom resize
Kamil ... how reproducable is this issue? Can you also attach /tmp/*log* when the problem occurs?
this was discussed at the blocker meeting today. we generally agreed that we
don't have a sufficiently solid base of shrink code to expect all shrink
operations to work, so we won't generally take shrink failures as blockers.
however, if this causes any pre-existing data to be lost, corrupted or
otherwise damaged, that could be a blocker. can you please test whether the
failure causes any adverse effects for the existing data? or does the shrink
just fail without actually touching the existing data in any way? thanks.
Fedora Bugzappers volunteer triage team
This bugreport simply states, that resizing encrypted partitions (not inside LVM) is not possible. There was no data loss, because there was no process executed. The GUI simply does not offer any possibility to do that. Wizard offers you only resizing of boot partition (of course useless) and custom partition dialog does not allow you to specify any number except zero to the particular field (didn't try to accept zero size). So surely there were no data loss and it is then probably not a blocker.
I don't think there is anything interesting in the logs, but I can recreate the layout if required. Maybe this should be seen more as a feature request. Currently you must resize encrypted partitions manually before install, because anaconda can't do it.
How do you resize an encrypted partition?
You mean by hand? I have googled up some guides and they worked :) Usually the guides describe resizing combination of dm-crypt and LVM and it's quite complicated. For the simple case of just dm-crypt (this case), I believe it is enough to:
1. if you want to enlarge partition, first enlarge dm-crypt area by "cryptsetup resize", then grow the partition, then grow the filesystem
2. if you want to shrink partition, first shrink filesystem, then shrink partition and then (maybe optionally) shrink dm-crypt are by "cryptsetup resize".
But I don't guarantee the exact approach. I believe I have seen some howto on the very site belonging to dm-crypt, but I can't find the link now.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
I don't really see that this is a 'common bugs' issue. I mean, nothing breaks, the installer really behaves as it should - it can't shrink encrypted partitions, so it doesn't offer to. If this needs to be documented anywhere, it's in the installation guide, not common bugs. Dropping from common bugs list.
Fedora Bugzappers volunteer triage team
dlehman, as this is about dmcrypt I'm going to assign this to you, feel free
to punt it over to David as it is about resizing, or to declare this something we don't want to support.
Release note flag is set because we need to fix documentation - see comment 9
As per Comment #9, Removed the "Requires Release Notes" flag,
and triaged this one to the install-guide.
um, that wasn't really desireable, the anaconda team did seem to want to keep this open and assigned to them as a feature request. we simply want the fact that this feature isn't implemented yet mentioned in the install guide _as well_.
Back to anaconda and I'll clone this ticket for the User Guide.
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. 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 WONTFIX if it remains open with a Fedora
'version' of '12'.
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 prior to Fedora 12's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
Still the same with anaconda-14.22.
Removing myself for these bug components as I'm either no longer involved in that aspect of the project, or no longer care to watch this particular bug. Sorry if you are caught in a maelstrom of bug changes as a result!
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.