Bug 538445 - Resizing encrypted devices is unsupported
Summary: Resizing encrypted devices is unsupported
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora Documentation
Classification: Retired
Component: user-guide
Version: devel
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Pete Travis
QA Contact: Ruediger Landmann
URL:
Whiteboard:
Depends On: 533350
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-18 16:01 UTC by eric
Modified: 2013-06-28 15:12 UTC (History)
9 users (show)

Fixed In Version:
Clone Of: 533350
Environment:
Last Closed: 2013-06-28 15:12:32 UTC
Embargoed:


Attachments (Terms of Use)

Description eric 2009-11-18 16:01:53 UTC
+++ This bug was initially created as a clone of Bug #533350 +++

Created an attachment (id=367805)
my layout

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):
anaconda 12.44

How reproducible:
always

--- Additional comment from kparal on 2009-11-06 05:33:58 EDT ---

Created an attachment (id=367806)
trying to shrink partition

--- Additional comment from kparal on 2009-11-06 05:34:21 EDT ---

Created an attachment (id=367807)
using custom resize

--- Additional comment from jlaska on 2009-11-06 12:56:44 EDT ---

Kamil ... how reproducable is this issue?  Can you also attach /tmp/*log* when the problem occurs?

--- Additional comment from awilliam on 2009-11-06 13:10:36 EDT ---

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
https://fedoraproject.org/wiki/BugZappers

--- Additional comment from kparal on 2009-11-09 07:48:26 EDT ---

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.

--- Additional comment from clumens on 2009-11-10 09:27:35 EDT ---

How do you resize an encrypted partition?

--- Additional comment from kparal on 2009-11-10 10:43:36 EDT ---

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.

--- Additional comment from fedora-triage-list on 2009-11-16 10:12:49 EDT ---


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:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

--- Additional comment from awilliam on 2009-11-17 02:12:15 EDT ---

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
https://fedoraproject.org/wiki/BugZappers

--- Additional comment from hdegoede on 2009-11-17 08:31:58 EDT ---

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.

--- Additional comment from ddumas on 2009-11-17 09:15:48 EDT ---

Release note flag is set because we need to fix documentation - see comment 9

--- Additional comment from dlehman on 2009-11-17 11:49:25 EDT ---

FWIW: http://www.saout.de/tikiwiki/tiki-index.php?page=ResizeLUKSPartitions

--- Additional comment from rlerch on 2009-11-17 19:34:29 EDT ---

As per Comment #9,  Removed the "Requires Release Notes" flag,
and triaged this one to the install-guide.

cheers,
ryanlerch

--- Additional comment from awilliam on 2009-11-17 22:00:14 EDT ---

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_.

--- Additional comment from eric on 2009-11-18 11:01:17 EDT ---

Back to anaconda and I'll clone this ticket for the User Guide.

Comment 1 John J. McDonough 2010-03-06 19:25:40 UTC
Triage information: This is not rocket science, but sufficiently involved that it should probably be left to the Guide owner

Comment 2 Florian Nadge 2011-10-07 12:00:01 UTC
Right(In reply to comment #1)
> Triage information: This is not rocket science, but sufficiently involved that
> it should probably be left to the Guide owner

Right, will take care of this.

Comment 3 Karsten Wade 2011-12-14 03:46:48 UTC
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!

Comment 5 Pete Travis 2013-06-17 16:26:16 UTC
We've somewhat formally deprecated the user guide in favor of the wholly adequate upstream DE documentation[1]. Is there now a plan to resurrect it?


[1] https://lists.fedoraproject.org/pipermail/docs/2013-April/014913.html

Comment 6 Pete Travis 2013-06-28 15:12:32 UTC
Since there isn't anyone working on this bug or guide, I'm closing the bug.


Note You need to log in before you can comment on or make changes to this bug.