From: Peter Smith <peter.smith@utsouthwestern.edu>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Wrecked Logical Volume with vgreduce --removemissing
Date: Wed, 06 Sep 2006 11:29:23 -0500 [thread overview]
Message-ID: <44FEF763.9040609@utsouthwestern.edu> (raw)
In-Reply-To: <20060904040917.25836.qmail@web30308.mail.mud.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 2685 bytes --]
What if you do "lvdisplay -m /dev/VolGroup00/LogVol00 --partial"
P
Tom+Dale wrote:
> I had a bad drive in my volume group, so I tried "vgreduce
> --removemissing VolGroup00" which seemed to work. Then, I tried
> "vgchange -ay --partial VolGroup00" which also appeared to complete
> successfully. It seems like I was partly successful but I cannot get
> the logical volume to be recognized. I don't know what else to do?
> Where can I learn more about LVM? How does one utilize the LVM
> archive or backup files? Can't seem to find an answer to this
> problem. Is all of my data lost?
>
> [root[at]server ~]# lvchange -vvvay /dev/VolGroup00/LogVol00
> Processing: lvchange -vvvay /dev/VolGroup00/LogVol00
> O_DIRECT will be used
> Setting global/locking_type to 1
> Setting global/locking_dir to /var/lock/lvm
> File-based locking enabled.
> Using logical volume(s) on command line
> Locking /var/lock/lvm/V_VolGroup00 WB
> Opened /dev/sda RW
> /dev/sda: block size is 4096 bytes
> /dev/sda: No label detected
> Opened /dev/hda1 RW
> /dev/hda1: block size is 1024 bytes
> /dev/hda1: No label detected
> Opened /dev/hda2 RW
> /dev/hda2: block size is 4096 bytes
> /dev/hda2: No label detected
> Opened /dev/hda3 RW
> /dev/hda3: block size is 4096 bytes
> /dev/hda3: No label detected
> Opened /dev/hda5 RW
> /dev/hda5: block size is 512 bytes
> /dev/hda5: lvm2 label detected
> lvmcache: /dev/hda5 now orphaned
> lvmcache: /dev/hda5 now in VG VolGroup00
> Opened /dev/hdb RW
> /dev/hdb: block size is 4096 bytes
> /dev/hdb: lvm2 label detected
> lvmcache: /dev/hdb now orphaned
> lvmcache: /dev/hdb now in VG VolGroup00
> /dev/hda5: lvm2 label detected
> /dev/hdb: lvm2 label detected
> /dev/hda5: lvm2 label detected
> /dev/hdb: lvm2 label detected
> Read VolGroup00 metadata (11) from /dev/hda5 at 18944 size 720
> /dev/hda5: lvm2 label detected
> /dev/hdb: lvm2 label detected
> Read VolGroup00 metadata (11) from /dev/hdb at 16896 size 720
> One or more specified logical volume(s) not found.
> Unlocking /var/lock/lvm/V_VolGroup00
> Closed /dev/sda
> Closed /dev/hda1
> Closed /dev/hda2
> Closed /dev/hda3
> Closed /dev/hda5
> Closed /dev/hdb
>
> ------------------------------------------------------------------------
> Do you Yahoo!?
> Get on board. You're invited
> <http://us.rd.yahoo.com/evt=40791/*http://advision.webevents.yahoo.com/mailbeta>
> to try the new Yahoo! Mail.
>
>------------------------------------------------------------------------
>
>_______________________________________________
>linux-lvm mailing list
>linux-lvm@redhat.com
>https://www.redhat.com/mailman/listinfo/linux-lvm
>read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
[-- Attachment #2: Type: text/html, Size: 3520 bytes --]
next prev parent reply other threads:[~2006-09-06 16:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 14:29 [linux-lvm] Ran vgreduce --missing to remove broken disk, am I screwed? Thomas Novin
2006-08-29 21:02 ` Thomas Novin
2006-08-29 21:16 ` Peter Smith
2006-08-30 2:16 ` Tom+Dale
2006-08-30 3:09 ` Tom+Dale
2006-09-04 4:09 ` [linux-lvm] Wrecked Logical Volume with vgreduce --removemissing Tom+Dale
2006-09-06 16:29 ` Peter Smith [this message]
2006-09-07 17:18 ` Peter Smith
2006-09-11 19:05 ` Tom+Dale
2006-09-12 18:06 ` Peter Smith
2006-09-10 17:27 ` Nix
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=44FEF763.9040609@utsouthwestern.edu \
--to=peter.smith@utsouthwestern.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.