Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 88224 - Awkward reaction to loopback encrypted filesystems
Awkward reaction to loopback encrypted filesystems
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Brock Organ
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2003-04-07 16:10 EDT by Mark Stoneburner
Modified: 2007-04-18 12:52 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-21 16:37:47 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mark Stoneburner 2003-04-07 16:10:41 EDT
My /home is encrypted so that I mount it through AES loopback. It is mentioned
in /etc/fstab in normal manner. My swap is similarly encrypted. Redhat installer
assumed the filesystem is messed up, and aborted the installer. Everything
worked fine when uncommented /home and swap partitions from fstab.

I realize this is not an ordinary situation, but instead of simply aborting the
installation when weird looking filesystem contents are encountered, it'd be
nice if the installer either

- offered to ignore that filesystem in the installation, or

- told the user to uncomment the filesystems from /etc/fstab if wants the
installer to ignore them

The relevant lines in my /etc/fstab are:

/dev/hdd3               /home   ext3   
defaults,loop=/dev/loop1,encryption=AES128   0 0
/dev/hdd4               swap     swap    sw,loop=/dev/loop6,encryption=AES192  
     0 0
Comment 1 Jeremy Katz 2003-05-16 17:14:43 EDT
We don't currently support using the crypto loop stuff in the userspace tools,
so this is a little tricky to handle.  I'll try to add something to do a little
better, but the current case might be the best that's possible until we
integrate crypto loop support for the distro.
Comment 2 W. Michael Petullo 2005-08-07 12:00:35 EDT
Cryptoloop has been replaced with dm-crypt.  This bug is very old.  Is this 
still relevant?  Does anaconda complain about dm-crypt filesystems?
Comment 3 Jeremy Katz 2005-09-21 16:37:47 EDT
This isn't really relevant anymore now that cryptoloop is obsoleted.  We don't
really handle dm-crypt, but the reaction should be better

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