From: Bernd Eckenfels <ecki@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: [2.4.1] mkreiserfs on loopdevice freezes kernel
Date: Wed, 31 Jan 2001 05:23:05 +0100 [thread overview]
Message-ID: <20010131052305.A828@lina.inka.de> (raw)
Hello,
if I run mkreiserfs on a 32megablocks /dev/loop0 it will lock up while
generating the journaling information. Sometimes at 20% sometimes at 60%.
Since mkreiserfs is not using the kernel module i guess this is a loop
device problem in 2.4.1 kernels.
There is no dmesg message at the lookup. mkreiserfs is in state 'D'. The
system issomewhat useable (X) but some programs just lock in syscalls (no su
or login possible).
If I run losetup -d /dev/loop0 on that device i will get a message that it
is busy, but the program will not return enymore. It is in 'D' also.
This is an unecncrypted loop device on a ext2 filesystem on a AIC-7861. Loop
is autoloaded as a module.
Wanted to try reiserfs with some verbose debugging for some time. Well,
perhaps md is my friend...
Greetings
Bernd
--
(OO) -- Bernd_Eckenfels@Wendelinusstrasse39.76646Bruchsal.de --
( .. ) ecki@{inka.de,linux.de,debian.org} http://home.pages.de/~eckes/
o--o *plush* 2048/93600EFD eckes@irc +497257930613 BE5-RIPE
(O____O) When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-31 4:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 4:23 Bernd Eckenfels [this message]
[not found] ` <Pine.SOL.4.21.0101310923480.29972-100000@green.csi.cam.ac.uk>
2001-01-31 22:27 ` reiserfs min size (was: [2.4.1] mkreiserfs on loopdevice freezes kernel) Bernd Eckenfels
2001-01-31 23:15 ` James Sutherland
2001-01-31 23:31 ` Bernd Eckenfels
2001-02-01 16:49 ` Chris Mason
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=20010131052305.A828@lina.inka.de \
--to=ecki@lina.inka.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