Re: zLinux instance on Mod3 and need to move to a Mod 9
Will a cp command correctly copy links and other special files? What I¹ve always seen suggested would be to mount the filesystems as you described, and then use a command such as: cd /mnt/3390-3 ; tar cf - * | (cd ../3390-9 tar xf -) tar will copy everything correctly. This will work cross-system as well, with a slight change in syntax: cd /mnt/3390-3 ; tar cf - * | ssh [EMAIL PROTECTED] cd /dirToLoad tar xf -¹ -- .~.Robert P. Nix Mayo Foundation /V\RO-OE-5-55 200 First Street SW / ( ) \ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but ³Join the story... Ride Ural.² in practice, theory and practice are different. On 7/23/07 3:56 PM, Jones, Zachary [EMAIL PROTECTED] wrote: On a second Linux machine, attach both drives to the Linux guest. Bring each dasd online to the linux guest. # chccwdev --online 0.0. device address Find out the Linux device # lsdasd Use the Linux device to mount the drives. mount the 3390-3 as /mnt/3390-3 mount the 3390-9 as /mnt/3390-9 then do a recursive copy of the 3390-3 to the 3390-9 # cp -R /mnt/3390-3/* /mnt/3390-9 On Mon, 2007-07-23 at 15:45 -0500, McKown, John wrote: DFDSS will copy the data from a -3 to a -9 with no problems. However, it will not resize the Linux partition or filesystem on that drive. You'd need to do a TRACK copy using DFDSS. The way that I would do it is to mount the -3 filesystem on a second Linux, mount the -9 filesystem as well, then tar to copy the data from the -3 to the -9. Of course, this is very slow, comparatively. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Sikich, Frank J. Sent: Monday, July 23, 2007 3:40 PM To: IBMVM@LISTSERV.UARK.EDU Subject: zLinux instance on Mod3 and need to move to a Mod 9 To All: I know this has been asked before and I tried to search the archives but was unsuccessful. I have a zLinux instance on a Mod 3 and I need to move it to a mod 9. I was successful in moving a mod 9 to another mod 9 using ADRDSSU from the zOS side. I don¹t this move will work using this method and was wondering if DDR is my only option to achieve the move. We are not using SFS. Any help would be useful Thanks Frank Sikich --- ***National City made the following annotations --- This communication is a confidential and proprietary business communication. It is intended solely for the use of the designated recipient(s). If this communication is received in error, please contact the sender and delete this communication. === Zachary Jones Operations Systems Analyst Northroup Grumman at City Of Grand Rapids, Michigan Office phone: 616-456-3456
Re: zLinux instance on Mod3 and need to move to a Mod 9
Will a cp command correctly copy links and other special files? No. But the three archivers I am familiar with will: tar, cpio, and rsync. (perhaps others too) Use tar. -- R;
Re: zLinux instance on Mod3 and need to move to a Mod 9
On Jul 24, 2007, at 8:10 AM, Richard Troth wrote: Will a cp command correctly copy links and other special files? No. But the three archivers I am familiar with will: tar, cpio, and rsync. (perhaps others too) Use tar. Well, GNU cp, with the -a option, will. Other cps can do something similar with some combination of flags. But use tar anyway. Adam
Re: zLinux instance on Mod3 and need to move to a Mod 9
On Mon, 23 Jul 2007, Paul Raulerson wrote: Well, yeah, but that won???t make the DASD bootable. You need to copy over the boot sector as well, dd if=/dev/dasda1 of=/dev/dasdb1 bs=512 count=1 I believe the current DASD driver will get it right: dd if=/dev/dasda of=/dev/dasdb where if you copy the whole disk you'll get a working bootstrap. But this requires that the disk was formatted with 'dasdfmt' ahead of time. More accurately, it requires that the target was formatted with the same layout as the source. Adam's point is important. ZIPL is not only traditional but is the only way to be sure you have a bootstrap on the target disk that has been put in the right place (from what ZIPL can determine). The CDL layout in particular does funny things (my term) with track 0. -- R;
Re: zLinux instance on Mod3 and need to move to a Mod 9
Some time back I had to something like this. I was brand new to Linux and used the cp -R. Seemed to go ok but the numbers didn't match up when I finished. After talking with someone else he suggested I redo it using tar. The tar solution worked a lot better. Seems there are certain types of links that don't get handled correctly. Definitely go the tar route. Bob Bates Enterprise Hosting Services - z/VM and z/Linux w. (972) 753-5967 c. (214) 907-5071 “This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rick Troth Sent: Tuesday, July 24, 2007 8:26 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux instance on Mod3 and need to move to a Mod 9 On Mon, 23 Jul 2007, Paul Raulerson wrote: Well, yeah, but that won’t make the DASD bootable. You need to copy over the boot sector as well, dd if=/dev/dasda1 of=/dev/dasdb1 bs=512 count=1 I believe the current DASD driver will get it right: dd if=/dev/dasda of=/dev/dasdb where if you copy the whole disk you'll get a working bootstrap. But this requires that the disk was formatted with 'dasdfmt' ahead of time. More accurately, it requires that the target was formatted with the same layout as the source. Adam's point is important. ZIPL is not only traditional but is the only way to be sure you have a bootstrap on the target disk that has been put in the right place (from what ZIPL can determine). The CDL layout in particular does funny things (my term) with track 0. -- R;
Re: zLinux instance on Mod3 and need to move to a Mod 9
zipl as far as I can tell, does not write out the boot sector on the DASD the same way, or at least it does not appear to. Running zipl on a freshly copied volume here will not result in a DASD unit that will IPL. dd will. As to traditional - well - dd pretty well predates zipl and chgroot; we were doing it in the late 1970's. ;) -Paul ---BeginMessage--- On Jul 23, 2007, at 8:43 PM, Paul Raulerson wrote: Well, yeah, but that won’t make the DASD bootable. You need to copy over the boot sector as well, dd if=/dev/dasda1 of=/dev/dasdb1 bs=512 count=1 (substitute the correct devices in the above command of course. The first one is the 3390-3 and the second the 3390-9. I have not tested this on a zSeries machine, but it should work just fine.) A chroot and running zipl is more traditional. Adam ---End Message---
Re: zLinux instance on Mod3 and need to move to a Mod 9
On Jul 24, 2007, at 10:54 AM, Paul Raulerson wrote: zipl as far as I can tell, does not write out the boot sector on the DASD the same way, or at least it does not appear to. Running zipl on a freshly copied volume here will not result in a DASD unit that will IPL. dd will. As to traditional - well - dd pretty well predates zipl and chgroot; we were doing it in the late 1970's. ;) If zipl does NOT write a boot sector, then that is a reportable bug. You might need to rerun mkinitrd too. However, the whole point of zipl is that it writes an IPL record to your DASD. Adam
Re: zLinux instance on Mod3 and need to move to a Mod 9
The command you showed will copy the entire drive - the extra commands cause dd to copy only the boot sector. You really need to run a mkinitrd before you run the zipl, so as far as I can see, traditional or not, zipl does not seem to do the job until you can IPL from the pack. -Paul ---BeginMessage--- On Mon, 23 Jul 2007, Paul Raulerson wrote: Well, yeah, but that won???t make the DASD bootable. You need to copy over the boot sector as well, dd if=/dev/dasda1 of=/dev/dasdb1 bs=512 count=1 I believe the current DASD driver will get it right: dd if=/dev/dasda of=/dev/dasdb where if you copy the whole disk you'll get a working bootstrap. But this requires that the disk was formatted with 'dasdfmt' ahead of time. More accurately, it requires that the target was formatted with the same layout as the source. Adam's point is important. ZIPL is not only traditional but is the only way to be sure you have a bootstrap on the target disk that has been put in the right place (from what ZIPL can determine). The CDL layout in particular does funny things (my term) with track 0. -- R; ---End Message---
Re: zLinux instance on Mod3 and need to move to a Mod 9
On Jul 24, 2007, at 11:25 AM, Paul Raulerson wrote: The command you showed will copy the entire drive - the extra commands cause dd to copy only the boot sector. You really need to run a mkinitrd before you run the zipl, so as far as I can see, traditional or not, zipl does not seem to do the job until you can IPL from the pack. Running mkinitrd has nothing to do with whether or not the pack is already IPLable. If the following does not work, then it is, I believe, a reportable defect in zipl: 1) mount the new disk somewhere; let's call it /mnt 2) copy the files to the new disk (cp -ax / /mnt, or (cd /; tar clf - | (cd /mnt; tar xf -)) 3) create enough static devices to get yourself going--I *think* this is just /dev/console, but different distros might have different ideas: mknod /mnt/dev/console c 5 1). Probably MAKEDEV -d /mnt/dev is the safest way although it will eat a little diskspace for devices you don't need before the /dev overmount 4) mount --bind /proc /mnt/proc (might not be needed, but won't hurt) 5) mount --bind /dev /mnt/dev 6) chroot /mnt 7) run mkinitrd with the appropriate-to-your-site parms 8) zipl 9) exit the chroot 10) umount /mnt/dev 11) umount /mnt/proc Adam
zLinux instance on Mod3 and need to move to a Mod 9
To All: I know this has been asked before and I tried to search the archives but was unsuccessful. I have a zLinux instance on a Mod 3 and I need to move it to a mod 9. I was successful in moving a mod 9 to another mod 9 using ADRDSSU from the zOS side. I don't this move will work using this method and was wondering if DDR is my only option to achieve the move. We are not using SFS. Any help would be useful Thanks Frank Sikich --- ***National City made the following annotations --- This communication is a confidential and proprietary business communication. It is intended solely for the use of the designated recipient(s). If this communication is received in error, please contact the sender and delete this communication. ===
Re: zLinux instance on Mod3 and need to move to a Mod 9
DFDSS will copy the data from a -3 to a -9 with no problems. However, it will not resize the Linux partition or filesystem on that drive. You'd need to do a TRACK copy using DFDSS. The way that I would do it is to mount the -3 filesystem on a second Linux, mount the -9 filesystem as well, then tar to copy the data from the -3 to the -9. Of course, this is very slow, comparatively. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Sikich, Frank J. Sent: Monday, July 23, 2007 3:40 PM To: IBMVM@LISTSERV.UARK.EDU Subject: zLinux instance on Mod3 and need to move to a Mod 9 To All: I know this has been asked before and I tried to search the archives but was unsuccessful. I have a zLinux instance on a Mod 3 and I need to move it to a mod 9. I was successful in moving a mod 9 to another mod 9 using ADRDSSU from the zOS side. I don't this move will work using this method and was wondering if DDR is my only option to achieve the move. We are not using SFS. Any help would be useful Thanks Frank Sikich --- ***National City made the following annotations --- This communication is a confidential and proprietary business communication. It is intended solely for the use of the designated recipient(s). If this communication is received in error, please contact the sender and delete this communication. ===
Re: zLinux instance on Mod3 and need to move to a Mod 9
On a second Linux machine, attach both drives to the Linux guest. Bring each dasd online to the linux guest. # chccwdev --online 0.0. device address Find out the Linux device # lsdasd Use the Linux device to mount the drives. mount the 3390-3 as /mnt/3390-3 mount the 3390-9 as /mnt/3390-9 then do a recursive copy of the 3390-3 to the 3390-9 # cp -R /mnt/3390-3/* /mnt/3390-9 On Mon, 2007-07-23 at 15:45 -0500, McKown, John wrote: DFDSS will copy the data from a -3 to a -9 with no problems. However, it will not resize the Linux partition or filesystem on that drive. You'd need to do a TRACK copy using DFDSS. The way that I would do it is to mount the -3 filesystem on a second Linux, mount the -9 filesystem as well, then tar to copy the data from the -3 to the -9. Of course, this is very slow, comparatively. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Sikich, Frank J. Sent: Monday, July 23, 2007 3:40 PM To: IBMVM@LISTSERV.UARK.EDU Subject: zLinux instance on Mod3 and need to move to a Mod 9 To All: I know this has been asked before and I tried to search the archives but was unsuccessful. I have a zLinux instance on a Mod 3 and I need to move it to a mod 9. I was successful in moving a mod 9 to another mod 9 using ADRDSSU from the zOS side. I don’t this move will work using this method and was wondering if DDR is my only option to achieve the move. We are not using SFS. Any help would be useful Thanks Frank Sikich --- ***National City made the following annotations --- This communication is a confidential and proprietary business communication. It is intended solely for the use of the designated recipient(s). If this communication is received in error, please contact the sender and delete this communication. === Zachary Jones Operations Systems Analyst Northroup Grumman at City Of Grand Rapids, Michigan Office phone: 616-456-3456
Re: zLinux instance on Mod3 and need to move to a Mod 9
Well, yeah, but that won’t make the DASD bootable. You need to copy over the boot sector as well, dd if=/dev/dasda1 of=/dev/dasdb1 bs=512 count=1 (substitute the correct devices in the above command of course. The first one is the 3390-3 and the second the 3390-9. I have not tested this on a zSeries machine, but it should work just fine.) -Paul From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Jones, Zachary Sent: Monday, July 23, 2007 3:57 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux instance on Mod3 and need to move to a Mod 9 On a second Linux machine, attach both drives to the Linux guest. Bring each dasd online to the linux guest. # chccwdev --online 0.0. device address Find out the Linux device # lsdasd Use the Linux device to mount the drives. mount the 3390-3 as /mnt/3390-3 mount the 3390-9 as /mnt/3390-9 then do a recursive copy of the 3390-3 to the 3390-9 # cp -R /mnt/3390-3/* /mnt/3390-9 On Mon, 2007-07-23 at 15:45 -0500, McKown, John wrote: DFDSS will copy the data from a -3 to a -9 with no problems. However, it will not resize the Linux partition or filesystem on that drive. You'd need to do a TRACK copy using DFDSS. The way that I would do it is to mount the -3 filesystem on a second Linux, mount the -9 filesystem as well, then tar to copy the data from the -3 to the -9. Of course, this is very slow, comparatively. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Sikich, Frank J. Sent: Monday, July 23, 2007 3:40 PM To: IBMVM@LISTSERV.UARK.EDU Subject: zLinux instance on Mod3 and need to move to a Mod 9 To All: I know this has been asked before and I tried to search the archives but was unsuccessful. I have a zLinux instance on a Mod 3 and I need to move it to a mod 9. I was successful in moving a mod 9 to another mod 9 using ADRDSSU from the zOS side. I don’t this move will work using this method and was wondering if DDR is my only option to achieve the move. We are not using SFS. Any help would be useful Thanks Frank Sikich --- ***National City made the following annotations --- This communication is a confidential and proprietary business communication. It is intended solely for the use of the designated recipient(s). If this communication is received in error, please contact the sender and delete this communication. === Zachary Jones Operations Systems Analyst Northroup Grumman at City Of Grand Rapids, Michigan Office phone: 616-456-3456
