The current patch to baselayout attempts to setup dm-crypt loopback systems during the checkfs phase, so that they can eventually be mounted by localmount. However, suppose the loopback file exists on a filesystem not initially mounted (such as /home, or /var and so on). It won't get setup properly during the checkfs phase since /home hasn't been mounted, and if it did get loaded during the localmount phase, what happens to possible loopback systems within that? It seems some form of sorting is needed to figure out the best order to mount and cryptsetup the various bits that need starting up. This is mostly here as a marked so that people getting errors can find out why. Hopefully one day though, this may get fixed... Reproducible: Always Steps to Reproduce: 1. Make a loopback system, store the file on a secondary mount point (/var, /usr or something). 2. Change the config files as normal, so that the loopback should be loaded. 3. Reboot. Actual Results: The loopback file could not be found because the filesystem it was on had not been mounted yet. Expected Results: The ordering be rearranged so that everything that needed to be mounted was and the loopback system be mounted as well.
Additional comments can be found from the original patch, at http://bugs.gentoo.org/show_bug.cgi?id=73598 .
This is something that requires a fairly wide ranging changes and is not within scope for me right now as I don't use loopback filesystems myself.
