The 701 mdisk statement for the target newclone is incorrect. 
David Kreuter

-------- Original message --------
From: "Nix, Robert P." <nix.rob...@mayo.edu> 
Date: 12-04-2013  09:24  (GMT-05:00) 
To: LINUX-390@VM.MARIST.EDU 
Subject: Re: sles11.2 mount logical volumes by path 
 
Actually, both entries are correct. The first minidisk on the volume is 500
cyl. The second starts at 501 and has 32259 cyl. I see nothing wrong with
this.

-- 
Robert P. Nix | Sr It Systems Engineer |  Systems Maintenance Services
507-284-0844 | nix.rob...@mayo.edu
Mayo Clinic| 200 First Street SW | Rochester, MN 55905
http://www.mayoclinic.org  | http://www.facebook.com/MayoClinic  |
http://www.youtube.com/mayoclinic  | http://twitter.com/mayoclinic




On 12/3/13 5:27 PM, "Scott Rohling" <scott.rohl...@gmail.com> wrote:

> Yes - wasn't sure if you'd typo'd entering them or these were actually the
> directory entries..    if the latter - yep - you'll be missing 500 cyls on
> your LVM disks.
> 
> Anyway - easy mistake ..   I assume the correct sizes will make it all work
> again  :)
> 
> 
> p.s.  your 202 should remain 32259 ..  it's got a 500 cylinder 191 disk in
> front of it (awful big disk!  we should talk about a common Linux guest 191
> .. you should not really need a r/w disk CMS disk for a Linux guest)
> 
> Scott Rohling
> 
> 
> On Tue, Dec 3, 2013 at 1:24 PM, Dean, David (I/S) <david_d...@bcbst.com>wrote:
> 
>> Scott, I think you've got it, I will try tomorrow.  Look at the LVM DASD
>> sizes, I made the same mistake again! Hard to put 6 gallons in a 5 gallon
>> bucket.  I will let you know.
>> 
>> -----Original Message-----
>> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
>> Scott Rohling
>> Sent: Tuesday, December 03, 2013 2:51 PM
>> To: LINUX-390@VM.MARIST.EDU
>> Subject: Re: sles11.2 mount logical volumes by path
>> 
>> Is the clone directory entry a typo?   32259 instead of 32759 ?   Your gold
>> image also uses 32259 for the 202 disk.. so a little confusing in the
>> numbers between the 2 directory entries -- I didn't notice this at first
>> glance..
>> 
>> From what you list - your sizes don't match - but I would think the
>> DDR/FLASHCOPY would fail or at least complain if those are the actual
>> values you're using..
>> 
>> Scott Rohling
>> 
>> 
>> On Tue, Dec 3, 2013 at 9:28 AM, Dean, David (I/S) <david_d...@bcbst.com
>>> wrote:
>> 
>>> REFERENCE DASD IN STRING BELOW
>>> 
>>> New Clone
>>> Three "blank" DASD
>>> 
>>> Cpfmtxa BA4d
>>> Format
>>> 000 end
>>> Label   l12501
>>> 
>>> Cpfmtxa BB50
>>> Format
>>> 000 end
>>> Label   l12502
>>> 
>>> Cpfmtxa BC4A
>>> Format
>>> 000 end
>>> Label   l12503
>>> 
>>> FLASHCOPY C74D 000 END BA4D 000 END SAVELABEL FLASHCOPY C650 000 END
>>> BB50 000 END SAVELABEL FLASHCOPY C651 000 END BC4A 000 END SAVELABEL
>>> 
>>> GOLD IMAGE USER DIR
>>> 
>>> USER LNXGLD XXXXX 1024M 1024M
>>>  INCLUDE LINDFLT
>>>  MDISK 191 3390 0001 0500 LGLD01 MR READ WRITE MULTIPLE  MDISK 202
>>> 3390 0501 32259 LGLD01 MR READ WRITE MULTIPLE  MDISK 700 3390 0001
>>> 32759 LGLD02 MR READ WRITE MULTIPLE  MDISK 701 3390 0001 32759 LGLD03
>>> MR READ WRITE MULTIPLE
>>> 
>>> NEW CLONE USER DIR
>>> 
>>> USER LNX125 XXXXX 1024M 1024M
>>>  INCLUDE LINDFLT
>>>  MDISK 191 3390 0001 0500 L12501 MR READ WRITE MULTIPLE  MDISK 202
>>> 3390 0501 32259 L12501 MR READ WRITE MULTIPLE  MDISK 700 3390 0001
>>> 32259 L12502 MR READ WRITE MULTIPLE  MDISK 701 3390 0001 32259 L12503
>>> MR READ WRITE MULTIPLE
>>> 
>>> 
>>> AFTER THE FLASHCOPY (OR DDR) I BRING UP THE "NEW CLONE", LOGIN IN,
>>> CHANGE IP INFO, AND I AM DONE.
>>> 
>>> lnxgld:/ # pvdisplay
>>>   --- Physical volume ---
>>>   PV Name               /dev/dasdc1
>>>   VG Name               vg1
>>>   PV Size               22.49 GiB / not usable 1.36 MiB
>>>   Allocatable           yes (but full)
>>>   PE Size               4.00 MiB
>>>   Total PE              5757
>>>   Free PE               0
>>>   Allocated PE          5757
>>>   PV UUID               EFMyi9-pjxQ-vGwt-ieZI-CcgA-Sp5A-2LXrF0
>>> 
>>>   --- Physical volume ---
>>>   PV Name               /dev/dasdb1
>>>   VG Name               vg1
>>>   PV Size               22.49 GiB / not usable 1.36 MiB
>>>   Allocatable           yes (but full)
>>>   PE Size               4.00 MiB
>>>   Total PE              5757
>>>   Free PE               0
>>>   Allocated PE          5757
>>>   PV UUID               uEiwua-aooC-XYIY-GH8b-BQVV-Nfi3-Gm9vzx
>>> 
>>> nxgld:/ # lvdisplay
>>>   --- Logical volume ---
>>>   LV Name                /dev/vg1/lv1
>>>   VG Name                vg1
>>>   LV UUID                fJ0chp-pW7a-bTdq-peCs-TmD2-ILHc-pJAydj
>>>   LV Write Access        read/write
>>>   LV Status              available
>>>   # open                 1
>>>   LV Size                44.98 GiB
>>>   Current LE             11514
>>>   Segments               2
>>>   Allocation             inherit
>>>   Read ahead sectors     auto
>>>   - currently set to     1024
>>>   Block device           253:0
>>> 
>>> lnxgld:/ # vgdisplay
>>>   --- Volume group ---
>>>   VG Name               vg1
>>>   System ID
>>>   Format                lvm2
>>>   Metadata Areas        2
>>>   Metadata Sequence No  2
>>>   VG Access             read/write
>>>   VG Status             resizable
>>>   MAX LV                0
>>>   Cur LV                1
>>>   Open LV               1
>>>   Max PV                0
>>>   Cur PV                2
>>>   Act PV                2
>>>   VG Size               44.98 GiB
>>>   PE Size               4.00 MiB
>>>   Total PE              11514
>>>   Alloc PE / Size       11514 / 44.98 GiB
>>>   Free  PE / Size       0 / 0
>>>   VG UUID               l9PjbN-u8Ai-8BxO-d3sf-6KAM-htkA-uIf72w
>>> 
>>> 
>>> 
>>> 
>>> 
>>> -----Original Message-----
>>> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
>>> Scott Rohling
>>> Sent: Tuesday, December 03, 2013 10:56 AM
>>> To: LINUX-390@VM.MARIST.EDU
>>> Subject: Re: sles11.2 mount logical volumes by path
>>> 
>>> Since it looks like you're DDRing a whole DASD rather then a minidisk --
>>>  are you relabelling, etc?    I'm confused from your example what you're
>>> cloning and how..      Can you show us the directory entry?
>>> 
>>> Scott Rohling
>>> 
>>> 
>>> On Tue, Dec 3, 2013 at 7:20 AM, Dean, David (I/S)
>>> <david_d...@bcbst.com
>>>> wrote:
>>> 
>>>> Ouch, you are right, I cut and pasted the wrong line.  It should
>>>> have been the /dev/vg1/lv1, sorry about that.  However the problem
>>>> is that in the past we just DDR'd or flashcopied only the three DASD
>>>> we use and everything worked, has this changed, or am I just missing
>> something?
>>>> 
>>>> Example (I hope  this formats right)
>>>> 
>>>> DASD  "gold"                 DASD "new clone"
>>>> 
>>>> C74d                    -->     BA4D
>>>>         191
>>>>         202 OS
>>>> 
>>>> C650    LVM             -->     BB50
>>>> C651    LVM             -->     BC4A
>>>> 
>>>> 
>>>> Maybe I should not have attended college in the 70's..?
>>>> 
>>>> 
>>>> 
>>>> -----Original Message-----
>>>> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf
>>>> Of Michael MacIsaac
>>>> Sent: Tuesday, December 03, 2013 9:56 AM
>>>> To: LINUX-390@VM.MARIST.EDU
>>>> Subject: Re: sles11.2 mount logical volumes by path
>>>> 
>>>> David,
>>>> 
>>>> Logical volumes are usually referenced in /etc/fstab by their /dev
>> entry.
>>>> For example:
>>>> 
>>>>   /dev/opt_vg/opt_lv   /opt                 ext3       acl,user_xattr
>>   1
>>>> 2
>>>> 
>>>> That is probably why by-path is not an option.
>>>> 
>>>> Then you write:
>>>>>  caught this when I DDR'd our "golden image" and attempted to
>>>>> bring it up and it cannot find  and mount
>>>>> " /dev/disk/by-path/ccw-0.0.0202-part1 /                    ext3
>>>> acl,user_xattr        1 1
>>>> 
>>>> This entry does not look like a logical volume, rather a
>>>> conventional file system on a minidisk.
>>>> 
>>>> To clone Linux systems that contain LVs with DDR, just copy all the
>>>> PVs (minidisks).  Linux will put the PVs, VGs and LVs back together
>>>> on the clone.
>>>> 
>>>> Hope this helps.
>>>> 
>>>> "Mike MacIsaac" <mikemac at-sign us.ibm.com>
>>>> 
>>>> --------------------------------------------------------------------
>>>> -- For LINUX-390 subscribe / signoff / archive access instructions,
>>>> send email to lists...@vm.marist.edu with the message: INFO
>>>> LINUX-390 or visit
>>>> http://www.marist.edu/htbin/wlvindex?LINUX-390
>>>> --------------------------------------------------------------------
>>>> -- For more information on Linux on System z, visit
>>>> http://wiki.linuxvm.org/
>>>> -----------------------------------------------------
>>>> Please see the following link for the BlueCross BlueShield of
>>>> Tennessee E-mail disclaimer:
>>>> http://www.bcbst.com/email_disclaimer.shtm
>>>> 
>>>> --------------------------------------------------------------------
>>>> -- For LINUX-390 subscribe / signoff / archive access instructions,
>>>> send email to lists...@vm.marist.edu with the message: INFO
>>>> LINUX-390 or visit
>>>> http://www.marist.edu/htbin/wlvindex?LINUX-390
>>>> --------------------------------------------------------------------
>>>> -- For more information on Linux on System z, visit
>>>> http://wiki.linuxvm.org/
>>>> 
>>> 
>>> ----------------------------------------------------------------------
>>> For LINUX-390 subscribe / signoff / archive access instructions, send
>>> email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
>>> visit
>>> http://www.marist.edu/htbin/wlvindex?LINUX-390
>>> ----------------------------------------------------------------------
>>> For more information on Linux on System z, visit
>>> http://wiki.linuxvm.org/
>>> -----------------------------------------------------
>>> Please see the following link for the BlueCross BlueShield of
>>> Tennessee E-mail disclaimer:
>>> http://www.bcbst.com/email_disclaimer.shtm
>>> 
>>> ----------------------------------------------------------------------
>>> For LINUX-390 subscribe / signoff / archive access instructions, send
>>> email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
>>> visit
>>> http://www.marist.edu/htbin/wlvindex?LINUX-390
>>> ----------------------------------------------------------------------
>>> For more information on Linux on System z, visit
>>> http://wiki.linuxvm.org/
>>> 
>> 
>> ----------------------------------------------------------------------
>> For LINUX-390 subscribe / signoff / archive access instructions, send
>> email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
>> http://www.marist.edu/htbin/wlvindex?LINUX-390
>> ----------------------------------------------------------------------
>> For more information on Linux on System z, visit http://wiki.linuxvm.org/
>> -----------------------------------------------------
>> Please see the following link for the BlueCross BlueShield of Tennessee
>> E-mail disclaimer:  http://www.bcbst.com/email_disclaimer.shtm
>> 
>> ----------------------------------------------------------------------
>> For LINUX-390 subscribe / signoff / archive access instructions,
>> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
>> visit
>> http://www.marist.edu/htbin/wlvindex?LINUX-390
>> ----------------------------------------------------------------------
>> For more information on Linux on System z, visit
>> http://wiki.linuxvm.org/
>> 
> 
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Reply via email to