SLES-9 does not use the /proc/scsi/zfcp/add_map interface

The Linux on zSeries FCP redbook has an example chapter on adding a SCSI
volume to a SLES-9 system - check p 142 in section 6.3.1

http://www.redbooks.ibm.com/abstracts/sg246344.html





Jay Brenneman

Linux Test and Integration Center

T/L:       295 - 7745
Extern: 845 - 435 - 7745
[EMAIL PROTECTED]





             "Seader, Cameron"
             <[EMAIL PROTECTED]
             er.com>                                                    To
             Sent by: Linux on         [EMAIL PROTECTED]
             390 Port                                                   cc
             <[EMAIL PROTECTED]
             IST.EDU>                                              Subject
                                       FW: Cloneing Linux Guests on FCP
                                       SCSI
             26/10/2004 02:13
             PM


             Please respond to
             Linux on 390 Port






im assuming i will have to issue the following command before i do a
mkinitrd on the target system.
echo "0x8d01 0x01:0x5005076300c50bdf 0x00:0x5000000000000000" >
/proc/scsi/zfcp/add_map

are there any other files that need to be edited for zfcp? I am running
SLES 9.
Are there any other scsi config files i need to be aware of?

-Cameron

-----Original Message-----
From: Carsten Otte [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 26, 2004 01:34
To: Linux on 390 Port
Cc: Seader, Cameron
Subject: Re: Cloneing Linux Guests on FCP SCSI



Yea, cloning a scsi volume is pretty easy. Those volumes are just plain
block devices (n blocks with all the
same size) like fba dasd, and you can copy all meta-information (partition
table, boot record and such) by
copying the entire volume:
- configure both disks online in a running Linux system [that does _not_
reside on either of those disks]
- verify that the disk size is equal:
        issue
                $bash> cat /proc/partitions
        the block count value for both disks must be equal
        the block count value for partitions may be different

        Example: [with ide, but is same for scsi except that devices are
named "sd?" instead of "hd?"]
                major minor  #blocks  name
                     3     0   75051217 hda
                   3     1   10032088 hda1
                   3     2     506520 hda2
                   3     3    2003400 hda3
                   3     4          1 hda4
                   3     5   39070080 hda5
                   3     64   75051217 hdb
                    3     65   60032088 hdb1
                    3     66    1506520 hdb2
        Above example looks fine, because hda and hdb do have the same
#blocks counter [hda1 and hdb1 differ, but that does not matter]
- issue a dd command to move the data: [example: clone source disk sdx to
target disk sdy]
        $bash> dd if=/dev/sdx of=/dev/sdy bs=512
- reread the partition table from the target volume:
        $bash> blockdev --rereadpt /dev/sdy
- sync disks
        $bash> sync
--> done

with kind regards
Carsten Otte
--
omnis enim res, quae dando non deficit, dum habetur et non datur, nondum
habetur, quomodo habenda est



        "Seader, Cameron" <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>


25/10/2004 04:51 PM
Please respond to Linux on 390 Port



        To:        [EMAIL PROTECTED]
        cc:
        Subject:        Cloneing Linux Guests on FCP SCSI




Greetings,
We are migrating all systems to FCP SCSI, and before when we were under
DASD we could do cloning really easy with ddr. Is there a way now to clone
when you are under FCP SCSI? is there some doc out there that has a howto
for this? I guess its pretty much the same except you have to use copy
services, and then somehow you have to change the FCP map within the guest.
Any ideas?

-Cameron Seader

This transmission may contain information that is privileged, confidential
and/or exempt from disclosure under applicable law. If you are not the
intended recipient, you are hereby notified that any disclosure, copying,
distribution, or use of the information contained herein (including any
reliance thereon) is STRICTLY PROHIBITED. If you received this transmission
in error, please immediately contact the sender and destroy the material in
its entirety, whether in electronic or hard copy format. Thank you. A1.

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390






[INFO] -- Access Manager:
This transmission may contain information that is privileged, confidential
and/or exempt from disclosure under applicable law.  If you are not the
intended recipient, you are hereby notified that any disclosure, copying,
distribution, or use of the information contained herein (including any
reliance thereon) is STRICTLY PROHIBITED. If you received this transmission
in error, please immediately contact the sender and destroy the material in
its entirety, whether in electronic or hard copy format.  Thank you.   A2


----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to