All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Wysochanski <dwysocha@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH] Avoid scanning all pvs in the system if pvcreating on a device with mdas.
Date: Wed, 17 Mar 2010 13:32:27 -0400	[thread overview]
Message-ID: <1268847147.2476.2.camel@f10-node1> (raw)
In-Reply-To: <87r5nj8d7b.fsf@twilight.int.mornfall.net.>

On Wed, 2010-03-17 at 11:17 +0100, Petr Rockai wrote:
> Hi,
> 
> Dave Wysochanski <dwysocha@redhat.com> writes:
> > Other areas of the code check whether there are mdas on an orphan pv before
> > doing the expensive scan of the system.  This patch adds this check to pvcreate
> > as well, and so will avoid the unnecessary scan if pvcreate on a device that
> > is an orphan PV.
> Looks OK to me. As far as I can tell, it should never happen that the
> metadata is out-of-date and we overwrite a non-orphan PV mistakenly.
> 
> This would require that the metadata on the PV claim this is an orphan
> but a newer copy of the metadata elsewhere claims this is part of a
> VG. That would mean that vgextend (or similar) failed to update the
> metadata on the new PV, which would presumably lead to overall vgextend
> failure and no new metadata on the pre-existing PVs either. So this
> should be safe.
> 

Ok - turns out I should have searched more carefully as there are more
instances where we could save the scanning.

I'll work on an updated patch.





  reply	other threads:[~2010-03-17 17:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-16 22:33 [PATCH] Avoid scanning all pvs in the system if pvcreating on a device with mdas Dave Wysochanski
2010-03-17 10:17 ` Petr Rockai
2010-03-17 17:32   ` Dave Wysochanski [this message]
2010-03-17 17:59     ` [PATCH] Avoid scanning all pvs in the system if operating " Dave Wysochanski
2010-03-18  0:47       ` Alasdair G Kergon
2010-03-18  1:05   ` [PATCH] Avoid scanning all pvs in the system if pvcreating " Alasdair G Kergon

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=1268847147.2476.2.camel@f10-node1 \
    --to=dwysocha@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.