All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Krichel <krichel@openlib.org>
To: Linux LVM <linux-lvm@redhat.com>
Cc: Bob Parks <bparks@wustl.edu>
Subject: [linux-lvm] uuid already in use
Date: Tue, 8 Jan 2008 11:55:28 -0600	[thread overview]
Message-ID: <20080108175528.GA6100@openlib.org> (raw)


  Hi,

  I have a disk /dev/hdb that appears to be physically
  damaged. It is in a volume group vg1. At some 
  stage it was so bad that I could not see it

raneb:# fdisk /dev/hdb

Unable to open /dev/hdb

  I ran 

raneb:# vgreduce vg1 --removemissing

  but could not restore the volume group to run,
  it kept complaing that /dev/hdb was missing.

  I read 

http://www.novell.com/communities/node/1502/recovering+lost+lvm+volume+disk

  and tried to apply the procedure described in the
  section "disk permanently removed". I first had
  to order a new disk. A new 500G disk arrived today.

  After a long shutdown, today the disk appears
  visible again, miraculously. 

raneb:/etc/lvm/archive# fdisk -l /dev/hdb

Disk /dev/hdb: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/hdb1               1       24321   195358401   83  Linux

  So I try to see it in lvm

raneb:/etc/lvm/archive# pvdisplay 
  Warning: Volume Group vg1 is not consistent
  --- Physical volume ---
  PV Name               /dev/hdd1
  VG Name               vg1
  PV Size               186.31 GB / not usable 3.69 MB
  Allocatable           yes 
  PE Size (KByte)       4096
  Total PE              47694
  Free PE               47694
  Allocated PE          0
  PV UUID               vy3MOc-47sl-zUal-nhdO-FFX3-ispO-Rl0h8p
   
  --- Physical volume ---
  PV Name               /dev/hdc
  VG Name               vg1
  PV Size               465.76 GB / not usable 4.02 MB
  Allocatable           yes 
  PE Size (KByte)       4096
  Total PE              119234
  Free PE               119234
  Allocated PE          0
  PV UUID               NxRIE1-ROxx-pfjJ-QHzh-7B80-F7wt-kRCmSK
   

  I try to recover the metadata. The correct one is in 
  vg1_00026.vg, because this is the version before the
  "vgreduce vg1 --removemissing". But

raneb:/etc/lvm/archive# pvcreate --uuid v3HXpi-d5QN-OGiW-VFBG-TNIY-qTun-bFhlVd  --restorefile vg1_00026.vg /dev/hdb
  uuid v3HXpi-d5QN-OGiW-VFBG-TNIY-qTun-bFhlVd already in use on "/dev/hdb1"

  I am puzzled. pvdisplay does not see the uuid value but
  pvcreate says it is is use?? What am I missing here?



  Cheers,

  Thomas Krichel                    http://openlib.org/home/krichel
                                RePEc:per:1965-06-05:thomas_krichel
                                               skype: thomaskrichel

             reply	other threads:[~2008-01-08 17:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 17:55 Thomas Krichel [this message]
2008-01-08 18:04 ` [linux-lvm] uuid already in use Bryn M. Reeves
2008-01-08 18:22   ` Thomas Krichel
2008-01-10  8:46     ` Thomas Krichel

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=20080108175528.GA6100@openlib.org \
    --to=krichel@openlib.org \
    --cc=bparks@wustl.edu \
    --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.