From: Matt <matt@bodgit-n-scarper.com>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OOPS] LVM and (I think) devfs
Date: Thu, 13 Dec 2001 10:07:43 +0000 [thread overview]
Message-ID: <20011213100743.A32449@mould.bodgit-n-scarper.com> (raw)
In-Reply-To: <20011212170921.A25596@mould.bodgit-n-scarper.com> <200112121726.fBCHQWu15088@vindaloo.ras.ucalgary.ca>
In-Reply-To: <200112121726.fBCHQWu15088@vindaloo.ras.ucalgary.ca>
On Wed, Dec 12, 2001 at 10:26:32AM -0700, Richard Gooch wrote:
> matt@bodgit-n-scarper.com writes:
> > Just started playing with LVM, (with devfs), and I've found I can reproduce
> > the attached oops consistently doing the following:
> >
> > # vgchange -a y
> > # vgchange -a n
> > # vgchange -a y
> >
> > Once this happens, the lvm becomes unreponsive and requires a reboot to
> > activate it again.
> >
> > It looks like the oops happens in devfs_open().
> >
> > I'm using 2.4.17-pre8 with LVM 1.0.1, and the kernel driver from
> > that package.
>
> Please try kernel 2.4.16 and see if the problem persists. There were
> devfs and minor LVM changes since then. Make sure you at least Cc: me.
I've tried just 2.4.17-pre8, without upgrading the LVM code, and the oops has
gone, I've tried a few repetitions of the above commands and it doesn't fall
over. There might be something iffy in the newer LVM code then...
Cheers
Matt
--
"Phase plasma rifle in a forty-watt range?"
"Only what you see on the shelves, buddy"
prev parent reply other threads:[~2001-12-13 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 17:09 Matt
2001-12-12 17:26 ` Richard Gooch
2001-12-12 20:54 ` Matt
2001-12-13 10:07 ` Matt [this message]
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=20011213100743.A32449@mould.bodgit-n-scarper.com \
--to=matt@bodgit-n-scarper.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
/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
all inboxes | Powered by JetHome®