Messages in this thread | | | Date | Thu, 31 Jul 2003 13:14:18 +0200 | From | Nico Schottelius <> | Subject | Re: bug in 2.6.0test2 |
| |
Steve Lord [Tue, Jul 29, 2003 at 06:43:17AM -0500]: > On Mon, 2003-07-28 at 17:26, Nico Schottelius wrote: > > Steve Lord [Mon, Jul 28, 2003 at 03:47:30PM -0500]: > > > > > > Something else went wrong before you crashed: > > > > > > bio too big device loop0 (2 > 0) > > > > > > This means you cannot use any bio larger than zero to this device, > > > > assume i didn't understand very much you told me..what is a bio? > > how do I use it? and why is it too big here? > > It looks like the loop device may not be correctly initialized yet, > no I/O is possible to it yet.
...we tried and experiement some more, here the results: - first we had old modutils (now: module-init-tools 0.9.13pre) - all modules are able to load now (loaded: aes,loop,cryptoloop) - losetup -e aes /dev/hda1 /dev/loop0 --> ioctl: LOOP_SET_FD: invalid argument - mount /dev/hda1 / -o loop,encryption=aes --> asks for pass, but doesn't unencrypt it --> it fails to mount the xfs filesystem below --> "mount: you must specify fs type..."
the filesystem on hda1 is encrypted with a 128 bit key / aes.
> > > which is probably why ext2 said this, since it caught the error when > > > building the bio. > > > > ext2? I am wondering..afai understood that, the root wasn't even > > decrypted, how can the kernel try to ext2-mount it?
oh..btw, the ramdisk is ext2..
> > > EXT2-fs: unable to read superblock > > > > > > XFS didn't catch the error building the bio and submitted it, at > > > which point the I/O tripped the BUG. I can fix this part, but > > > the original problem is something I know nothing about. > > > > ..or better why does it start mounting/before decrypt? > > > > I have never used a crypto loop device, so I cannot what is really > going on. Some initialization step may be missing in the loop device > which means it is not usable,
looks like the losetup is the problem...
> the mount it happening because the > kernel was told to mount it. If you are not specifying a filesystem > type, then possibly what is happening is it is attempting to open > the device as different filesystems, these all fail, until xfs > which does not detect the underlying error on the loop device, > and issues the IO which causes the BUG.
..which you are gonna fix ? :)
> So, we caused the crash, but you were on your way to one anyway, > eventually it would have failed to find a root device and given > up that way.
hopefully we'll get it soon.. my co-worker has to switch between 2.4 and 2.6 daily now..
Nico
-- echo God bless America | sed 's/.*\(A.*$\)/Why \1?/' pgp: new id: 0x8D0E27A4 | ftp.schottelius.org/pub/familiy/nico/pgp-key.new [unhandled content-type:application/pgp-signature] | |