From: Dennison Williams <evoltech@2inches.com>
Subject: ext3 filesystem is not recognized after losetup -e aes
Date: Fri, 04 Jan 2008 22:47:47 -0800
Message-ID: <477F2813.3010003@2inches.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
To: linux-crypto@vger.kernel.org
Sender: linux-crypto-owner@vger.kernel.org

Here is the setup: MD software RAID 5 on 4 disks (md0), a LVM logical
volume (/dev/volume_group/logical_volume) comprised of one physical
device (/dev/md0), a encryption layer provided by the cryptoloop driver
(losetup -e aes /dev/loop0 /dev/volume_group/logical_volume), then a
EXT3 file system (mkfs.ext3 /dev/loop0).

Recently the RAID device kicked out one of the disks during a large file
transfer. After re-adding the disk to the array whith "mdadm /dev/mdo
-add /dev/sde (smartctl didn't report
anything wrong with it, I am not sure why this happened), authenticating
against the cryptographic layer, then trying to mount the drive, I get
the following error:

[root@storage redhat]# mount -t ext3 /dev/loop1 /terrorbyte/1/
mount: wrong fs type, bad option, bad superblock on /dev/loop1,

The message in /var/log/message is:
VFS: Can't find ext3 filesystem on dev loop1.

I then tried to e2fsck the /dev/loop1 partition with all of the
different blocks that were reported from:
mke2fs -n /dev/loop1
with no luck still.

I don't think that LVM has anything to do with it, because on another
volume group, that didn't loose any drives, there is a encrypted logical
volume that has the same problem.  Actually all of the drives that I
have encrypted have this problem now. I am unsure of where the problem
actually is, and how to go about debugging it. Any suggestions would be
appreciated.

Sincerely,
Dennison Williams