From: Soeren Sonnenburg <kernel@nn7.de>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: loopback device + crypto = crash on 2.6.0-test7 ?
Date: Sun, 09 Nov 2003 13:23:01 +0100 [thread overview]
Message-ID: <1068380580.17223.5.camel@localhost> (raw)
In-Reply-To: <20031109131018.GA18342@deneb.enyo.de>
On Sun, 2003-11-09 at 14:10, Florian Weimer wrote:
> Soeren Sonnenburg wrote:
>
> > losetup -e blowfish /dev/loop0 /file
> > Password:
> > mkfs -t ext3 /dev/loop0
> > mount /dev/loop0 /mnt
> > <error unknown fs type>
> > <from here something was seriously broken... could not reboot anymore>
>
> I'm seeing something similar, but in my case, mke2fs already crashes.
Yes... it crashes somewhen after writing to the loop device... sometimes
mkfs is enough, sometimes one has to write a bit more...
> > system is:
> > Linux no 2.6.0-test7 #8 Sun Oct 26 17:00:49 CET 2003 ppc GNU/Linux
>
> Mine ist -test9 on x86.
>
> Have you found a solution in the meantime?
not me.
Soeren.
next prev parent reply other threads:[~2003-11-09 12:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 7:09 loopback device + crypto = crash on 2.6.0-test7 ? Soeren Sonnenburg
2003-11-07 14:01 ` Bill Davidsen
2003-11-09 13:10 ` Florian Weimer
2003-11-09 12:23 ` Soeren Sonnenburg [this message]
2003-11-10 22:41 ` bill davidsen
2003-11-10 23:27 ` Peter Lieverdink
2003-11-10 23:46 ` bill davidsen
2003-11-11 0:15 ` Linus Torvalds
2003-11-11 8:54 ` Florian Weimer
2003-11-11 2:50 ` Valdis.Kletnieks
2003-11-11 9:43 ` Peter Lieverdink
2003-11-11 16:49 ` Linus Torvalds
2003-11-16 8:46 ` Peter Lieverdink
2004-01-06 10:36 ` Peter Lieverdink
2004-01-06 10:53 ` Matthias Hentges
-- strict thread matches above, loose matches on Subject: below --
2003-11-15 13:13 Jindrich Makovicka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1068380580.17223.5.camel@localhost \
--to=kernel@nn7.de \
--cc=fw@deneb.enyo.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox