Cloned system mounts file systems read-only
Hi. From information I have gathered from this list I tried to clone a sles 9 system (lpar no VM). When I log in to the system and try to update a file I get a message that it is read-only. When I booted this system I see messages VFS: Mounted root (reiserfs filesystem) readonly Trying to move old root to /initrd . . . failed Unmounting old root Here are the steps I followed Shut down source linux system which uses dasd 43e and 43f Use VSE to fastcopy full volumes to another two dasd addresses 186 and 187 (3390-3) IPL source linux system chccwdev -e 0.0.0186and chccwdev -e 0.0.0187 lsdasd command to see that 186 is dasdc and 187 is dasdd mount /dev/dasdc1 /mnt chroot /mnt edit /etc/zipl.conf changing the parmfile dasd addresses from 43e and 43f to 186 and 187 ed /etc/hosts rename /etc/sysconfig/hardware hwcfg-dasd-bus-ccw-0.0.043e to .0186 and .043f to .0187 zipl exit out of chroot unmount /mnt chccwdev -d 0.0.0186 and 0187 logout If anyone can point out my fatal readonly flaw I would appreciate it. Thanks in advance from a very green newbie! Zoltan -- 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
Re: Cloned system mounts file systems read-only
Zoltan, Have you tried doing a mkinitrd just befor the zipl? Ron Herczeg, Zoltan wrote: Hi. From information I have gathered from this list I tried to clone a sles 9 system (lpar no VM). When I log in to the system and try to update a file I get a message that it is read-only. When I booted this system I see messages VFS: Mounted root (reiserfs filesystem) readonly Trying to move old root to /initrd . . . failed Unmounting old root Here are the steps I followed Shut down source linux system which uses dasd 43e and 43f Use VSE to fastcopy full volumes to another two dasd addresses 186 and 187 (3390-3) IPL source linux system chccwdev -e 0.0.0186and chccwdev -e 0.0.0187 lsdasd command to see that 186 is dasdc and 187 is dasdd mount /dev/dasdc1 /mnt chroot /mnt edit /etc/zipl.conf changing the parmfile dasd addresses from 43e and 43f to 186 and 187 ed /etc/hosts rename /etc/sysconfig/hardware hwcfg-dasd-bus-ccw-0.0.043e to .0186 and .043f to .0187 zipl exit out of chroot unmount /mnt chccwdev -d 0.0.0186 and 0187 logout If anyone can point out my fatal readonly flaw I would appreciate it. Thanks in advance from a very green newbie! Zoltan -- 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
Re: Cloned system mounts file systems read-only
You're not showing how you either ATTACHed or LINKed to the 186/187 -- you need to DETACH them. (vmcp det 186-187). Just putting them offline with chccwdev doesn't do it.. (unless your 'logout' is a LOGOFF -- if so, then I'm stumped) Hope that helps - Scott On Fri, Apr 18, 2008 at 7:15 AM, Herczeg, Zoltan [EMAIL PROTECTED] wrote: Hi. From information I have gathered from this list I tried to clone a sles 9 system (lpar no VM). When I log in to the system and try to update a file I get a message that it is read-only. When I booted this system I see messages VFS: Mounted root (reiserfs filesystem) readonly Trying to move old root to /initrd . . . failed Unmounting old root Here are the steps I followed Shut down source linux system which uses dasd 43e and 43f Use VSE to fastcopy full volumes to another two dasd addresses 186 and 187 (3390-3) IPL source linux system chccwdev -e 0.0.0186and chccwdev -e 0.0.0187 lsdasd command to see that 186 is dasdc and 187 is dasdd mount /dev/dasdc1 /mnt chroot /mnt edit /etc/zipl.conf changing the parmfile dasd addresses from 43e and 43f to 186 and 187 ed /etc/hosts rename /etc/sysconfig/hardware hwcfg-dasd-bus-ccw-0.0.043e to .0186 and .043f to .0187 zipl exit out of chroot unmount /mnt chccwdev -d 0.0.0186 and 0187 logout If anyone can point out my fatal readonly flaw I would appreciate it. Thanks in advance from a very green newbie! Zoltan -- 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
Re: Cloned system mounts file systems read-only
I don't think he was running in z/VM though... The two things I see as possible problems are that you didn't run mkinitrd before running zipl. The mkinitrd needs to know about the disks as well, based on your current chroot'ed paths. This is my absolute favorite mistake, and I've recovered from it dozens (and dozens) of times I do not learn quickly. The second, and it may have just been missed, would be that, once you've mkinitrd zipl'ed, you didn't mention getting out of the chroot environment, unmounting the paths and taking the devices offline again to Linux. Just jerking them out from beneath the system may have left them in an undesired state. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. On 4/18/08 8:47 AM, Scott Rohling [EMAIL PROTECTED] wrote: You're not showing how you either ATTACHed or LINKed to the 186/187 -- you need to DETACH them. (vmcp det 186-187). Just putting them offline with chccwdev doesn't do it.. (unless your 'logout' is a LOGOFF -- if so, then I'm stumped) Hope that helps - Scott On Fri, Apr 18, 2008 at 7:15 AM, Herczeg, Zoltan [EMAIL PROTECTED] wrote: Hi. From information I have gathered from this list I tried to clone a sles 9 system (lpar no VM). When I log in to the system and try to update a file I get a message that it is read-only. When I booted this system I see messages VFS: Mounted root (reiserfs filesystem) readonly Trying to move old root to /initrd . . . failed Unmounting old root Here are the steps I followed Shut down source linux system which uses dasd 43e and 43f Use VSE to fastcopy full volumes to another two dasd addresses 186 and 187 (3390-3) IPL source linux system chccwdev -e 0.0.0186and chccwdev -e 0.0.0187 lsdasd command to see that 186 is dasdc and 187 is dasdd mount /dev/dasdc1 /mnt chroot /mnt edit /etc/zipl.conf changing the parmfile dasd addresses from 43e and 43f to 186 and 187 ed /etc/hosts rename /etc/sysconfig/hardware hwcfg-dasd-bus-ccw-0.0.043e to .0186 and .043f to .0187 zipl exit out of chroot unmount /mnt chccwdev -d 0.0.0186 and 0187 logout If anyone can point out my fatal readonly flaw I would appreciate it. Thanks in advance from a very green newbie! Zoltan -- 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 -- 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
IBM - Java tool for System z trouble shooting and performance problems
Haven't tried this, but it looks interesting. quote JinsightLive for IBM(r) System z(tm) is a visualization tool that allows you to interactively trace and visualize the execution of a Java(tm) program on z/OS(r) or Linux(r) on System z (zLinux). The Java application can be running in a variety of runtime environments including CICS(r) and WebSphere(r) Application Server. The power of this tool is the ability to see and drill down to the lowest levels of the application in a visual manner. The tool is now available as a toolkit , free of charge. /quote http://www-1.ibm.com/support/docview.wss?rs=1083context=SSGMGVdc=D600; uid=swg21303088loc=en_UScs=UTF-8lang=enrss=ct1083other http://preview.tinyurl.com/5b295x -- 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
Re: IBM - Java tool for System z trouble shooting and performance problems
On Apr 18, 2008, at 10:22 AM, McKown, John wrote: Haven't tried this, but it looks interesting. quote JinsightLive for IBM(r) System z(tm) is a visualization tool that allows I have an end user who has been very excited about using this to profile his heavyweight tomcat apps. We've run into two issues so far: 1. the original release was for 31-bit JRE only. My end user was running a 64-bit JRE. Stop. Fortunately, IBM released an update in the last few weeks to bring support for 64-bit JREs. 2. It requires glibc-2.4. My end user is running SLES9, which does not have glibc-2.4. Stop. Our strategy now is to upgrade him to SLES10, which we were going to do eventually anyway, but the sudden requirement is still a disappointment. ok bear -- 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
