All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Berra <bluca@comedia.it>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Having duplicate PV problems, think there's a bug in LVM2 md component detection
Date: Mon, 28 Feb 2005 22:38:56 +0100	[thread overview]
Message-ID: <20050228213856.GA4151@percy.comedia.it> (raw)
In-Reply-To: <001301c51dd5$abc80860$32dcdc0a@vanish>

On Mon, Feb 28, 2005 at 03:39:59PM -0500, Ron Watkins wrote:
>Yes, I have two PVs with the same UUID.  The problem is that these PVs are 
>COMPONENTS OF an MD device.  So when pvcreate writes its superblock to md0, 
>it gets mirrored onto all the components of md0.  Later runs elicit much 
>complaining because /dev/hda and several /dev/sd devices now have the 
>'same' UUID.   They're SUPPOSED to, they're components of a RAID.
>
>LVM is supposed to detect this situation and not do that, but it doesn't 
>seem to be working for me.
>
i wonder if it is a problem with largefile access ?!?
which version of lvm2 are you using?
does debian patch it?
can you try stracing it an look for seeks, so we can see if it is
wrapping around somewhere?

L.

-- 
Luca Berra -- bluca@comedia.it
        Communication Media & Services S.r.l.
 /"\
 \ /     ASCII RIBBON CAMPAIGN
  X        AGAINST HTML MAIL
 / \

  reply	other threads:[~2005-02-28 21:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-26 20:30 [linux-lvm] Having duplicate PV problems, think there's a bug in LVM2 md component detection Ron Watkins
2005-02-28 11:15 ` go0ogl3
2005-02-28 20:39   ` Ron Watkins
2005-02-28 21:38     ` Luca Berra [this message]
2005-02-28 22:29       ` Ron Watkins
2005-03-01  7:38         ` Luca Berra
2005-03-01 14:58 ` Alasdair G Kergon
2005-03-02 18:25 ` [linux-lvm] " Matthias Julius

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=20050228213856.GA4151@percy.comedia.it \
    --to=bluca@comedia.it \
    --cc=linux-lvm@redhat.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.