[ If this is explained somewhere else (HOWTO or FAQ), please give me a pointer. ] Is there any way to mix loop-device (and in particular) loop-AES and ext3 together in data journaling mode? Ie. bottom -> to -> top ext3 - loop-AES - ext3 raw - loop-AES - ext3 Or am I shooting myself to leg, I am? BR, Jani -- Jani Averbach
On Wed, Feb 20, 2002 at 10:03:22PM +0200, Jani Averbach wrote:> > > [ If this is explained somewhere else (HOWTO or FAQ), please give me a > pointer. ] > > Is there any way to mix loop-device (and in particular) loop-AES and ext3 > together in data journaling mode? > > Ie. > bottom -> to -> top > ext3 - loop-AES - ext3 > raw - loop-AES - ext3http://www.eckner.org/crypto/index.html -- Ralf Hildebrandt (Im Auftrag des Referat V A) Ralf.Hildebrandt@charite.de Charite Campus Virchow-Klinikum Tel. +49 (0)30-450 570-155 Referat V A - Kommunikationsnetze - Fax. +49 (0)30-450 570-916 I almost died, but I made it, so I'm not so serious about formal-wear anymore. -- Gene Boggs
Jani Averbach wrote:> Is there any way to mix loop-device (and in particular) loop-AES and ext3 > together in data journaling mode?Device backed loops (ext3 -> loop -> device) don't have issues with ext3 or any other journaled filesystems. However, if loop is file backed (ext3 -> loop -> ext3 -> device), the underlying file system must be mounted data=journal or data=ordered. If underlying filesystem is mounted data=writeback or if it is plain old ext2, write ordering expectation by journaled filesystem (ext3, reiserfs, jfs, xfs, or whatever) on top of loop driver is not guaranteed, and journal replay may corrupt data. Use of non-journaled file systems on top of file backed loop don't have above mentioned write ordering issues, as they must be repaired using fsck, not by replaying journal. Regards, Jari Ruusu <jari.ruusu@pp.inet.fi>