All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Thornber <thornber@btconnect.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Nasty bug in lvm and/or md and/or reiserfs
Date: Thu, 26 Jul 2001 23:24:53 +0100	[thread overview]
Message-ID: <20010726232453.A1209@btconnect.com> (raw)
In-Reply-To: <20010726131928.D1779@linux.com>; from tack@linux.com on Thu, Jul 26, 2001 at 01:19:28PM -0400

On Thu, Jul 26, 2001 at 01:19:28PM -0400, Jason Tackaberry wrote:
> I have discovered one or more severe bugs in any or all of lvm, md, and
> reiserfs.  I'm not a kernel guy and I don't claim to know how these
> things are supposed to interact at that level, so I'm not going to point
> fingers.  Instead, here's what happened and I'll let you decide. :)
> 
> The problem surfaces when you create a volume group with lvm and include
> a partition that happens to be mounted.

This was a stupid thing to do; and yes we should probably check to see
if anyone else has the pv open when we do a pvcreate.  I will look into
it to see how much code needs to be changed.

pvcreate would have stamped it's own metadata over md's metadata, so
I'm not surprised md had trouble.  This is not a bug in md or
reiserfs, just user error that LVM should have caught.

- Joe

  parent reply	other threads:[~2001-07-26 22:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-26 17:19 [linux-lvm] Nasty bug in lvm and/or md and/or reiserfs Jason Tackaberry
2001-07-26 18:47 ` AJ Lewis
2001-07-26 20:07   ` Jason Tackaberry
2001-07-26 20:17     ` AJ Lewis
2001-07-27  6:57       ` Werner John
2001-07-27 13:02         ` Jason Tackaberry
2001-07-30  7:46           ` Werner John
2001-07-30 19:31             ` Ralph Jennings
2001-07-31  5:59               ` Werner John
2001-07-26 22:24 ` Joe Thornber [this message]
2001-07-26 21:44   ` Jason Tackaberry
  -- strict thread matches above, loose matches on Subject: below --
2001-07-27 15:20 Kevin M Corry
2001-07-27 15:51 ` Jason Tackaberry

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=20010726232453.A1209@btconnect.com \
    --to=thornber@btconnect.com \
    --cc=linux-lvm@sistina.com \
    /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.