From: Oleg Drokin <green@namesys.com>
To: Christian Jaeger <christian.jaeger@ethlife.ethz.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Lockups with loop'ed sparse files on reiserfs?
Date: Fri, 13 Jun 2003 19:56:34 +0400 [thread overview]
Message-ID: <20030613155634.GA18478@namesys.com> (raw)
In-Reply-To: <p04320407bb0f79fd523e@[192.168.3.11]>
Hello!
On Fri, Jun 13, 2003 at 03:38:44PM +0200, Christian Jaeger wrote:
> I've experienced 3 lockups in the last few days, all while using
> sparse files. Could also be problems with UML, SKAS, raid5 over loop
> device, or loop devices with vfat files, but it looks like the only
> common thing is sparse files on reiserfs.
>
> 1.) kernel 2.4.20 from debian unstable (= kernel.org kernel with
> quite a few security and other patches), additionally patched with
> kernel-patch-skas 3-1 from debian. Started user-mode-linux using a
> sparse file with an ext2 filesystem on it, using tap0 networking, did
> apt-get upgrade inside this uml (which started to download (and
> already unpack?) quite a bit of stuff), halfway through the whole
> (host) system froze. Still responded to pings, but telnet $host 80
> would not show any activity from running apache. Went to the server
> room, I could change virtual terminals with Alt-<number>, but could
> not log in. Reset.
Were there anything interesting on the console where your kernel outputs
its messages (the host kernel?)?
Any chance to hit say sysrq-T/sysrq-P to find out where CPU spins?
> I'd mainly like to know if all of what I did is supported or not.
Yes it is supported. I am doing this kind of stuff (with uml and skas3)
on reiserfs everyday and everything works just fine with 2.4.19, 1.4.20 and 2.4.21.
Bye,
Oleg
next prev parent reply other threads:[~2003-06-13 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 13:38 Lockups with loop'ed sparse files on reiserfs? Christian Jaeger
2003-06-13 15:56 ` Oleg Drokin [this message]
2003-06-13 15:59 ` Oleg Drokin
2003-06-13 18:07 ` Christian Jaeger
2003-06-13 20:22 ` Oleg Drokin
2003-06-14 23:10 ` Christian Jaeger
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=20030613155634.GA18478@namesys.com \
--to=green@namesys.com \
--cc=christian.jaeger@ethlife.ethz.ch \
--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