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
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.
Cryptoloop has been replaced with dm-crypt. This bug is very old. Is this
still relevant? Does anaconda complain about dm-crypt filesystems?
This isn't really relevant anymore now that cryptoloop is obsoleted. We don't
really handle dm-crypt, but the reaction should be better