From: "Rob Schwartz" <rschwartz@boscovs.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] best way to make lv with 3 500G luns
Date: Fri, 29 Jul 2005 17:49:34 -0400 [thread overview]
Message-ID: <00f001c59487$6857af80$6e09580a@b034547> (raw)
In-Reply-To: 42EAA2A9.1080107@deadhookers.org
I think you are on the right track... Your PV's don't look right but I am
not familiar with PV's on SCSI devs. Using the -v and -d options have
helped me a lot!!!
Good luck!!
----- Original Message -----
From: "Eric Wagar" <eric@deadhookers.org>
To: "LVM general discussion and development" <linux-lvm@redhat.com>
Sent: Friday, July 29, 2005 5:42 PM
Subject: Re: [linux-lvm] best way to make lv with 3 500G luns
> Rob Schwartz wrote:
>> Have you tried the vgcreate with the -v (for verbose) or -d (for debug)
>> options?
>> ----- Original Message ----- From: "Eric Wagar" <eric@deadhookers.org>
>> To: "LVM" <linux-lvm@redhat.com>
>> Sent: Friday, July 29, 2005 5:27 PM
>> Subject: [linux-lvm] best way to make lv with 3 500G luns
>>
>>
>>> What are the steps to create a volume comprised of 3 500G SGI TP9500
>>> LUNS on SLES9?
>>>
>>> I'm only able to get as far as pvcreate. Afterwards, I am unable to
>>> create a visible vg. By that I mean, I receive no error when I issue
>>> vgcreate, but I am unable to vgdisplay the new vg.
>>>
>>> This is on SLES9/SN2 with two module SGI A350 and using two FC paths.
> I had not used the -v or -d option prior to this, no. But, here is the
> information:
> assault /home/ericwa# pvcreate /dev/scsi/sdh8-0c0i0l9;pvcreate
> /dev/scsi/sdh8-0c0i1l8;pvcreate /dev/scsi/sdh5-0c0i1l10
> No physical volume label read from /dev/scsi/sdh8-0c0i0l9
> Physical volume "/dev/scsi/sdh8-0c0i0l9" successfully created
> No physical volume label read from /dev/scsi/sdh8-0c0i1l8
> Physical volume "/dev/scsi/sdh8-0c0i1l8" successfully created
> No physical volume label read from /dev/scsi/sdh5-0c0i1l10
> Physical volume "/dev/scsi/sdh5-0c0i1l10" successfully created
> ...
> assault /home/ericwa# vgcreate -v u018 /dev/scsi/sdh8-0c0i1l8
> /dev/scsi/sdh5-0c0i1l10 /dev/scsi/sdh8-0c0i0l9
> <snip>
> Adding physical volume '/dev/scsi/sdh8-0c0i1l8' to volume group 'u018'
> <snip>
> Adding physical volume '/dev/scsi/sdh5-0c0i1l10' to volume group 'u018'
> <snip>
> Adding physical volume '/dev/scsi/sdh8-0c0i0l9' to volume group 'u018'
> <snip>
> Archiving volume group "u018" metadata.
> Creating volume group backup "/etc/lvm/backup/u018"
> Volume group "u018" successfully created
> assault /home/ericwa# vgdisplay -v
> Finding all volume groups
> Found duplicate PV aLiq4sGKfFA2S2t77t8MU5V13Pe4C17K: using /dev/sdg not
> /dev/sdr
> Found duplicate PV DThr6w5xGUEOOflPTEpFnnyUp02BXODP: using /dev/sdw not
> /dev/sdah
> Found duplicate PV P5CU7BDZ9m4NdrJyR7BrhSZT3fVDV8HB: using /dev/sdx not
> /dev/sdai
> Found duplicate PV aLiq4sGKfFA2S2t77t8MU5V13Pe4C17K: using /dev/sdan not
> /dev/sdr
> Found duplicate PV DThr6w5xGUEOOflPTEpFnnyUp02BXODP: using /dev/sdl not
> /dev/sdah
> Found duplicate PV P5CU7BDZ9m4NdrJyR7BrhSZT3fVDV8HB: using /dev/sdm not
> /dev/sdai
> Found duplicate PV aLiq4sGKfFA2S2t77t8MU5V13Pe4C17K: using /dev/sdac not
> /dev/sdr
> Found duplicate PV DThr6w5xGUEOOflPTEpFnnyUp02BXODP: using /dev/sdas not
> /dev/sdah
> Found duplicate PV P5CU7BDZ9m4NdrJyR7BrhSZT3fVDV8HB: using /dev/sdat not
> /dev/sdai
> assault /home/ericwa# pvdisplay
> <snip>
> --- NEW Physical volume ---
> PV Name /dev/sdr
> VG Name
> PV Size 542.93 GB
> Allocatable NO
> PE Size (KByte) 0
> Total PE 0
> Free PE 0
> Allocated PE 0
> PV UUID aLiq4s-GKfF-A2S2-t77t-8MU5-V13P-e4C17K
>
> --- NEW Physical volume ---
> PV Name /dev/sdah
> VG Name
> PV Size 542.93 GB
> Allocatable NO
> PE Size (KByte) 0
> Total PE 0
> Free PE 0
> Allocated PE 0
> PV UUID DThr6w-5xGU-EOOf-lPTE-pFnn-yUp0-2BXODP
>
> --- NEW Physical volume ---
> PV Name /dev/sdai
> VG Name
> PV Size 542.93 GB
> Allocatable NO
> PE Size (KByte) 0
> Total PE 0
> Free PE 0
> Allocated PE 0
> PV UUID P5CU7B-DZ9m-4Ndr-JyR7-BrhS-ZT3f-VDV8HB
>
> All of the <snip> are the "Found duplicate PV" UUID lines. This system
> has two FC HBA's, one each connected to a FC switch, which has two ISL's,
> and then each switch has two paths to the TP9500 controllers.
>
> I am guessing, guessing since this is my first time to use LVM, that the
> output from pvdisplay showing "Allocatable NO" is bad. I have
> tried pvchange, but it seg faults.
>
> thanks
> eric
>
> _______________________________________________
> 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/
>
prev parent reply other threads:[~2005-07-29 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 21:27 [linux-lvm] best way to make lv with 3 500G luns Eric Wagar
2005-07-29 21:29 ` Rob Schwartz
2005-07-29 21:42 ` Eric Wagar
2005-07-29 21:49 ` Rob Schwartz [this message]
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='00f001c59487$6857af80$6e09580a@b034547' \
--to=rschwartz@boscovs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox