From: Stefan Traby <stefan@hello-penguin.com>
To: Mark Swanson <swansma@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: loop device corruption in 2.4.6
Date: Thu, 5 Jul 2001 07:29:29 +0200 [thread overview]
Message-ID: <20010705072929.A7922@stefan.sime.com> (raw)
In-Reply-To: <01070417140200.03178@test.home2.mark>
In-Reply-To: <01070417140200.03178@test.home2.mark>; from swansma@yahoo.com on Wed, Jul 04, 2001 at 05:14:02PM -0400
On Wed, Jul 04, 2001 at 05:14:02PM -0400, Mark Swanson wrote:
> I get repeatable errors with 2.4.6 patched with the international encryption
> patch patch-int-2.4.3.1.bz2 when building loop device filesystems on top of
> Reiserfs.
Well, exactly this happens here on 2.4.5 and earlier too...
I can't verify this on 2.4.6 (plain) because the kernel hangs right after
partition-check on my Thinkpad A21p. :(
--
ciao -
Stefan
CONFIG_HANG_AFTER_PARTITION_CHECK=y
next prev parent reply other threads:[~2001-07-05 5:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-04 21:14 loop device corruption in 2.4.6 Mark Swanson
2001-07-05 5:29 ` Stefan Traby [this message]
2001-07-05 10:18 ` Jari Ruusu
2001-07-05 11:39 ` Ian Stirling
2001-07-05 14:17 ` Mark Swanson
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=20010705072929.A7922@stefan.sime.com \
--to=stefan@hello-penguin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=swansma@yahoo.com \
/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