All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: lvm-devel@redhat.com
Subject: duplicate pv names
Date: Wed, 3 Apr 2013 11:22:37 -0400	[thread overview]
Message-ID: <20130403152237.GA1031@redhat.com> (raw)
In-Reply-To: <87r4isklih.fsf@mornfall.net>

On Wed, Apr 03, 2013 at 11:32:06AM +0200, Petr Rockai wrote:
> I ran into similar problems with a different set of patches, that remove
> pv_read. What I'll probably need to do is adding a list of devices to
> PVs, so we can check whether something on the command line matches any
> of the "duplicate" PVs.
> 
> I see you make quite heavy use of pv_read in your new version of
> process_each_pv. You can have a look at:
> 
> (git clone) http://repos.mornfall.net/lvm2/mornfall.git
> 
> branch "merged" or for more limited view of the pv_read removal patches,
> branch "lvmcache". (git checkout origin/merged).

I wish I'd known you were also working on toollib.c; we could have
coordinated the sequence of changes a little better.  Perhaps we could
all push our in-progress work to an lvm2.git branch like I've done in
http://git.fedorahosted.org/cgit/lvm2.git/log/?h=dev-dct-process-each

> It would be good if we could get rid of pv_read, as the code for
> handling nomda PVs is wrong anyway, and we always need to scan. I think
> the only remaining issue with the non-pv_read version is the duplicate
> handling as outlined above.

OK, it'll be nice to get rid of the nomda case.  I'll study your changes
further and try to rework my new process_each_pv to avoid using pv_read.
Perhaps you'll then be able to drop the toollib commit in your tree.



      reply	other threads:[~2013-04-03 15:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02 21:24 duplicate pv names David Teigland
2013-04-03  9:32 ` Petr Rockai
2013-04-03 15:22   ` David Teigland [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=20130403152237.GA1031@redhat.com \
    --to=teigland@redhat.com \
    --cc=lvm-devel@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.