From: James Hawtin <oolon@ankh.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM2 recovery on IP-SAN after OS re-install
Date: Tue, 29 May 2012 10:14:52 +0100 [thread overview]
Message-ID: <4FC4938C.7090503@ankh.org> (raw)
In-Reply-To: <CAGQjrKZ0CD7O8_KYBd+KvBmK0nnxxoWc+5sm0Pk+XYkZEq3vOQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
On 28/05/12 19:40, tariq wali wrote:
> Hi,
> We had an OS crash on x86_64 CentOS , LVM2 and it had 6TB LUN via
> IP SCSI SAN mounted to it and after the OS reinstall on a crash we
> had hard time to mount the original SAN volume as you can imagine 6TB
> of marketing data with 3 LVM partitions as data data1 and data2 .
> After troubleshooting almost for a day I was able to get the LVM
> metadata using dd from the SAN LUN /dev/sdd1 which I used to recreate
> and restore all LVM partitions back to original state , we sure became
> the raving fans of LVM today ! however after all the recovery I see
> this annoying warning each time I execute any of the lvm commands ..
>
> lvs
> * Found duplicate PV XtGmeFOiCTWpLBckKZKlGtYKPVdBgVJn: using
> /dev/sdd1 not/dev/sdc1*
> LV VG Attr LSize Origin Snap% Move Log Copy% Convert
> data vg0 -wi-ao 2.00T
> data1 vg0 -wi-ao 2.00T
> data2 vg0 -wi-ao 1.44T
>
1) The the same lun presented to the computer more than once? If this is
a deliberate thing for redundancy then your need to setup multipath to
take advantage use the devices in /dev/mapper of this and mask off the
raw /dev/sd? devices in your /etc/lvm/lvm.conf
2) Did you copy all the data from one disk to another? if so is the old
disk still available to the system?
3) Check you lun masking.
James
[-- Attachment #2: Type: text/html, Size: 2698 bytes --]
next prev parent reply other threads:[~2012-05-29 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 18:40 [linux-lvm] LVM2 recovery on IP-SAN after OS re-install tariq wali
2012-05-29 9:14 ` James Hawtin [this message]
2012-06-19 16:40 ` Bryn M. Reeves
2012-06-20 10:06 ` tariq wali
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=4FC4938C.7090503@ankh.org \
--to=oolon@ankh.org \
--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.