From: Sasha Z <kleptophobiac@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Can't restore the volume group after ghosting an hdd
Date: Tue, 22 Mar 2005 18:12:46 -0500 [thread overview]
Message-ID: <e5146c2a05032215124af3c0d7@mail.gmail.com> (raw)
I had a hard drive begin to go bad on me, so I ghosted it to another
drive. lvm2 successfully picked up on the ghosted drive and didn't
complain about it. I used pvmove to send the data off to other parts
of the array. I removed the hdd I ghosted to from the array, wiped it,
and readded it as a new drive.
Now I can't seem to put my array back together.
I'm worried about the output of the lvs command saying that the volume
group is inconsistent. What exactly does that mean, and what do I do
about it? I can still seem to mount everything ok and get to my data,
but these errors are disconcerting. Is there a way to get everything
back to "normal"?
pvs:
Found duplicate PV iCXUP4rdy2ZhoIJ4NWl1s3dr1au6QofX: using /dev/hdg1
not /dev/hdg
Found duplicate PV fFNJ9uKeNSMVQxwLH82lnI3J0hQYRKTh: using /dev/hdk1
not /dev/hdk
Warning: Volume Group vg0 is not consistent
PV VG Fmt Attr PSize PFree
/dev/hde4 vg0 lvm2 a- 179.75G 0
/dev/hdg vg0 lvm2 a- 172.55G 60.36G
/dev/hdi vg0 lvm2 a- 152.67G 152.67G
/dev/hdk vg0 lvm2 a- 233.76G 0
vgs:
Found duplicate PV iCXUP4rdy2ZhoIJ4NWl1s3dr1au6QofX: using /dev/hdg1
not /dev/hdg
Found duplicate PV fFNJ9uKeNSMVQxwLH82lnI3J0hQYRKTh: using /dev/hdk1
not /dev/hdk
VG #PV #LV #SN Attr VSize VFree
vg0 4 1 0 wz--n 738.73G 213.03G
lvs:
Found duplicate PV iCXUP4rdy2ZhoIJ4NWl1s3dr1au6QofX: using /dev/hdg1
not /dev/hdg
Found duplicate PV fFNJ9uKeNSMVQxwLH82lnI3J0hQYRKTh: using /dev/hdk1
not /dev/hdk
Volume group "vg0" inconsistent
LV VG Attr LSize Origin Snap% Move Copy%
lv0 vg0 -wi--- 525.70G
next reply other threads:[~2005-03-22 23:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 23:12 Sasha Z [this message]
2005-03-22 23:26 ` [linux-lvm] Can't restore the volume group after ghosting an hdd Alasdair G Kergon
2005-03-23 2:08 ` Sasha Z
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=e5146c2a05032215124af3c0d7@mail.gmail.com \
--to=kleptophobiac@gmail.com \
--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.