Once again: LPAR mode running SuSE Linux 7.2 (S390) - Kernel 2.4.7-SMP and moving to new dasd.
What about changing the current dasd addresses in the following: /boot/parmfile /proc/dasd/devices /etc/zipl.conf to the new dasd addresses. Run zipl? Anything else? Thanks, Craig -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Wednesday, March 08, 2006 5:11 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: New DASD > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > Behalf Of Kittendorf, Craig > Sent: Wednesday, March 08, 2006 4:04 PM > To: LINUX-390@VM.MARIST.EDU > Subject: New DASD > > > We're about to move our DASD to new Shark. Linux/390 is currently on > addresses 0FAA and 0FAB. The new device addresses on the > Shark will be > 7949 and 794A. > > Will Linus/390 automagically recognize these new devices? Or am I in > deep trouble? > > Thanks, > Craig > LPAR or z/VM mode? Under z/VM, just keep using the old virtual DASD addresses on the new real addresses by updating the z/VM directory for the z/Linux guest and go. If you're in an LPAR, then you're in deep kimchee. Of course, if the person doing the I/O gen is "nice" and you're in an LPAR, he can use HCD to "map" the old device numbers to the new DASD for that one LPAR. But I'll bet he or she isn't that "nice". Oh, and you'd need to somehow copy the entire volume to the new addresses. I think that DFDSS, or FDR can do this. Again, if you're under z/VM, then no changes are need other than to the directory for the z/Linux guest. -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology ---------------------------------------------------------------------- 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
