From: Faux Pas III <fauxpas@temp123.org>
To: linux-kernel@vger.kernel.org
Subject: 2.4.17 Oops, maybe LVM ?
Date: Wed, 13 Feb 2002 01:35:48 -0500 [thread overview]
Message-ID: <20020213063548.GA463@temp123.org> (raw)
I'm getting reproducible oopses whenever I pull a file over the network
off of my LVM filesystem, so not exactly sure where this is coming
from... this happens with vanilla 2.4.17 although the kernel that I
captured the oops output from has LVM 1.0.2 and posix acls patches on
it.
Raw oops text and ksymoops output are at http://www.burdell.org/~fauxpas/
--
Josh Litherland (fauxpas@temp123.org)
next reply other threads:[~2002-02-13 6:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 6:35 Faux Pas III [this message]
2002-02-13 9:07 ` 2.4.17 Oops, maybe LVM ? Joe Thornber
2002-02-13 13:47 ` Faux Pas III
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=20020213063548.GA463@temp123.org \
--to=fauxpas@temp123.org \
--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.