linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Phillip Susi <psusi@cfl.rr.com>
Subject: Re: [linux-lvm] getting pe_start right
Date: Fri, 06 May 2011 17:16:43 +0200	[thread overview]
Message-ID: <4DC410DB.1070404@redhat.com> (raw)
In-Reply-To: <4DC40BFD.3080408@cfl.rr.com>


On 05/06/2011 04:55 PM, Phillip Susi wrote:
> While trying to convert my mdadm raid5 array from metadata format 0.9 to 
> 1.0, I forgot to specify the version and it defaulted to 1.2, which 
> damaged the lvm metadata.  After correcting mdadm to 1.0, I decided to 
> try to recreate the LVM after managing to locate the volume descriptions 
> in the metadata after manually dumping it.
> 
> The problem I now have is that pvcreate will not use the same pe_start 
> as before.  It was 384 and it is now 3072.  I tried using --metadatasize 
> 192k --dataalignmentsize 0 and it did not help.  What gives?

Try to set
default_data_alignment = 0

from lvm.conf:
# Default alignment of the start of a data area in MB.  If set to 0,
# a value of 64KB will be used.  Set to 1 for 1MiB, 2 for 2MiB, etc.

Also, if you use

	pvcreate --uuid <pv uuid from metadata> --restorefile <old VG backup>

it should create PV exacltly as needed for olf VG (with --restorefile it uses
offset from metadata backup, overriding default)

Then vgcfgrestore and you should have exactly the same cfg.

Milan

  parent reply	other threads:[~2011-05-06 15:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06 14:55 [linux-lvm] getting pe_start right Phillip Susi
2011-05-06 15:05 ` CHANDRASEKARAN, GIRIDHAR (GIRI) (ATTSI)
2011-05-06 15:16 ` Milan Broz [this message]
2011-05-06 15:21 ` Mike Snitzer
2011-05-10 14:28   ` Phillip Susi

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=4DC410DB.1070404@redhat.com \
    --to=mbroz@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=psusi@cfl.rr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).