From: Faux Pas III <fauxpas@temp123.org>
To: Joe Thornber <joe@fib011235813.fsnet.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.17 Oops, maybe LVM ?
Date: Wed, 13 Feb 2002 08:47:25 -0500 [thread overview]
Message-ID: <20020213134725.GA755@temp123.org> (raw)
In-Reply-To: <20020213063548.GA463@temp123.org> <20020213090748.GA2421@fib011235813.fsnet.co.uk>
In-Reply-To: <20020213090748.GA2421@fib011235813.fsnet.co.uk>
On Wed, Feb 13, 2002 at 09:07:48AM +0000, Joe Thornber wrote:
> Do you have any other reason to suspect LVM ? eg, have you tried
> it successfully on a non-LVM device ?
It seems to only crash reliably when I pull a file off the filesystem
that's on the lv, but I haven't been at all scientific in determining
that. =) I'll try to kill it without LVM being in the picture.
> have you tried it without the acls patch ?
Yes. Still crashes under the same conditions with the 'eth0: Abnormal
interrupt' bit, but the oops might be very different. I'll try to get
an oops with a vanilla kernel...
--
Josh Litherland (fauxpas@temp123.org)
next prev parent reply other threads:[~2002-02-13 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 6:35 2.4.17 Oops, maybe LVM ? Faux Pas III
2002-02-13 9:07 ` Joe Thornber
2002-02-13 13:47 ` Faux Pas III [this message]
2002-02-13 16:29 ` Andreas Dilger
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=20020213134725.GA755@temp123.org \
--to=fauxpas@temp123.org \
--cc=joe@fib011235813.fsnet.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.