Guest configuration question
Have a development system that has 2 IFLs and both are configured to the LPAR running z/VM. Have several SUSE Linux 11 guests running and the LPAR is busy during the day - high 90s percent busy as displayed by Velocity. I noticed yesterday that two of the busier systems have *3* vCPUs configured to them. I'm wondering if that will hurt or help performance of the guest (or maybe be of no consequence) when the LPAR is very busy. Thanks, Joe -- 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/
Re: SLES11 boot problem
Thanks Ray, We actually circumvented the problem earlier this afternoon by disabling multipathing. Brought the system up in rescue mode, mounted /dev/sda3 (root) at /mnt, mounted /dev/sda1 to /mnt/boot, rebound proc, sys and dev then chroot /mnt. Edited /etc/sysconfig/kernel changing INITRD_MODULES=jbd ext3 zfcp dm-multipath to INITRD_MODULES=jbd ext3 zfcp then ran mkinitrd and zipl -V and rebooted successfully. However, we still don't understand why multipathing was broken. I have two other SuSE 11 guests running on this same zVM LPAR with multipathing enabled that weren't having any issues. None the less, just glad it's back. On Tue, Jan 12, 2010 at 4:01 PM, Raymond Higgs rayhi...@us.ibm.com wrote: Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 01/12/2010 10:09:09 AM: Joe Martin widet.jmar...@gmail.com Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 01/12/2010 10:09 AM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: SLES11 boot problem *Did that change anything?* - We don't think so. *when you get dumped into the shell, can you see any of your devices in /dev, or /proc/partitions? * Yes. *Is the zfcp driver loaded (cat /proc/modules)?* Yes. We see the disk, with the right path and lun number for each partition. Here?s the output from the shell: $ cd by-path $ ls -l total 0 lrwxrwxrwx 1 root root 9 Jan 12 14:45 ccw-0.0.d000-zfcp-0x5006048ad52cea89:0x07 01 - ../../sda lrwxrwxrwx 1 root root 10 Jan 12 14:45 ccw-0.0.d000-zfcp-0x5006048ad52cea89:0x07 01-part1 - ../../sda1 lrwxrwxrwx 1 root root 10 Jan 12 14:45 ccw-0.0.d000-zfcp-0x5006048ad52cea89:0x07 01-part2 - ../../sda2 lrwxrwxrwx 1 root root 10 Jan 12 14:45 ccw-0.0.d000-zfcp-0x5006048ad52cea89:0x07 01-part3 - ../../sda3 cat partitions major minor #blocks name 8 0 20971200 sda 8 1 522112 sda1 8 22096482 sda2 8 3 18338197 sda3 253 0 20971200 dm-0 253 1 522112 dm-1 253 22096482 dm-2 253 3 18338197 dm-3 $ Here?s the cat /proc/modules output from the shell: cat /proc/modules scsi_dh_alua 10688 0 - Live 0x03e000135000 scsi_dh_rdac 10196 0 - Live 0x03e000131000 scsi_dh_hp_sw 6584 0 - Live 0x03e000115000 scsi_dh_emc 11120 0 - Live 0x03eb1000 dm_round_robin 4504 1 - Live 0x03e55000 sd_mod 48336 1 - Live 0x03e00016c000 crc_t10dif 2288 1 sd_mod, Live 0x03e36000 dm_snapshot 25048 0 - Live 0x03e000129000 dm_multipath 26736 2 dm_round_robin, Live 0x03e000121000 dm_mod 97888 8 dm_snapshot,dm_multipath, Live 0x03ee8000 scsi_dh 10036 5 scsi_dh_alua,scsi_dh_rdac,scsi_dh_hp_sw,scsi_dh_emc,dm_multipath, Live 0x03ead000 zfcp 137304 1 [permanent], Live 0x03e000149000 qdio 65912 1 zfcp, Live 0x03e000103000 scsi_transport_fc 60180 1 zfcp, Live 0x03e45000 scsi_tgt 17544 1 scsi_transport_fc, Live 0x03e3f000 scsi_mod 247096 9 scsi_dh_alua,scsi_dh_rdac,scsi_dh_hp_sw,scsi_dh_emc,sd_mod,scs i_dh,zfcp,scsi_transport_fc,scsi_tgt, Live 0x03e6f000 ext3 199376 0 - Live 0x03eb6000 mbcache 11748 1 ext3, Live 0x03e39000 jbd 87624 1 ext3, Live 0x03e58000 $ May not be important but we had two other SLES11 guests in the same LPAR have the same problem (total of 3). zVM was restarted - the two other failing guests booted successfully. On Mon, Jan 11, 2010 at 3:30 PM, Mark Post mp...@novell.com wrote: On 1/11/2010 at 04:23 PM, Joe Martin widet.jmar...@gmail.com wrote: I did catch the error in the fstab and put the mount for /boot after the mount for /. Did that change anything? If not, when you get dumped into the shell, can you see any of your devices in /dev, or /proc/partitions? Is the zfcp driver loaded (cat /proc/modules)? Mark Post -- 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 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 Joe, Here are some things that I would check: Is the pchid online on the SE for d000? Is the chpid online on the SE for d000? Did someone change the NPIV settings on the SE for the chpid for d000? Were there any zoning changes? Did someone
Re: SLES11 boot problem
*Did that change anything?* - We don't think so. *when you get dumped into the shell, can you see any of your devices in /dev, or /proc/partitions? * Yes. *Is the zfcp driver loaded (cat /proc/modules)?* Yes. We see the disk, with the right path and lun number for each partition. Here’s the output from the shell: $ cd by-path $ ls -l total 0 lrwxrwxrwx 1 root root 9 Jan 12 14:45 ccw-0.0.d000-zfcp-0x5006048ad52cea89:0x07 01 - ../../sda lrwxrwxrwx 1 root root 10 Jan 12 14:45 ccw-0.0.d000-zfcp-0x5006048ad52cea89:0x07 01-part1 - ../../sda1 lrwxrwxrwx 1 root root 10 Jan 12 14:45 ccw-0.0.d000-zfcp-0x5006048ad52cea89:0x07 01-part2 - ../../sda2 lrwxrwxrwx 1 root root 10 Jan 12 14:45 ccw-0.0.d000-zfcp-0x5006048ad52cea89:0x07 01-part3 - ../../sda3 cat partitions major minor #blocks name 8 0 20971200 sda 8 1 522112 sda1 8 22096482 sda2 8 3 18338197 sda3 253 0 20971200 dm-0 253 1 522112 dm-1 253 22096482 dm-2 253 3 18338197 dm-3 $ Here’s the cat /proc/modules output from the shell: cat /proc/modules scsi_dh_alua 10688 0 - Live 0x03e000135000 scsi_dh_rdac 10196 0 - Live 0x03e000131000 scsi_dh_hp_sw 6584 0 - Live 0x03e000115000 scsi_dh_emc 11120 0 - Live 0x03eb1000 dm_round_robin 4504 1 - Live 0x03e55000 sd_mod 48336 1 - Live 0x03e00016c000 crc_t10dif 2288 1 sd_mod, Live 0x03e36000 dm_snapshot 25048 0 - Live 0x03e000129000 dm_multipath 26736 2 dm_round_robin, Live 0x03e000121000 dm_mod 97888 8 dm_snapshot,dm_multipath, Live 0x03ee8000 scsi_dh 10036 5 scsi_dh_alua,scsi_dh_rdac,scsi_dh_hp_sw,scsi_dh_emc,dm_multipath, Live 0x03ead000 zfcp 137304 1 [permanent], Live 0x03e000149000 qdio 65912 1 zfcp, Live 0x03e000103000 scsi_transport_fc 60180 1 zfcp, Live 0x03e45000 scsi_tgt 17544 1 scsi_transport_fc, Live 0x03e3f000 scsi_mod 247096 9 scsi_dh_alua,scsi_dh_rdac,scsi_dh_hp_sw,scsi_dh_emc,sd_mod,scs i_dh,zfcp,scsi_transport_fc,scsi_tgt, Live 0x03e6f000 ext3 199376 0 - Live 0x03eb6000 mbcache 11748 1 ext3, Live 0x03e39000 jbd 87624 1 ext3, Live 0x03e58000 $ May not be important but we had two other SLES11 guests in the same LPAR have the same problem (total of 3). zVM was restarted - the two other failing guests booted successfully. On Mon, Jan 11, 2010 at 3:30 PM, Mark Post mp...@novell.com wrote: On 1/11/2010 at 04:23 PM, Joe Martin widet.jmar...@gmail.com wrote: I did catch the error in the fstab and put the mount for /boot after the mount for /. Did that change anything? If not, when you get dumped into the shell, can you see any of your devices in /dev, or /proc/partitions? Is the zfcp driver loaded (cat /proc/modules)? Mark Post -- 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 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
SLES11 boot problem
Have a VM guest running SLES 11 - has been working fine for months - rebooted several times. Over the weekend there was a problem with the SAN switch and the guest lost it's paths to disk. Now when we try to boot the guest, we see the following. Waiting for device /dev/sda3 to appear: ok fsck 1.41.1 (01-Sep-2008) [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda3 fsck.ext3: Device or resource busy while trying to open /dev/sda3 Filesystem mounted or opened exclusively by another program? fsck failed. Mounting root device read-only. Mounting root /dev/sda3 mount -o ro,acl,user_xattr -t ext3 /dev/sda3 /root mount: /dev/sda3 already mounted or /root busy could not mount root filesystem -- exiting to /bin/sh We've booted the guest in repair mode. I initially used the Repair Installed System tool to repair the file system and it came back clean. I then logged onto the system using ssh and manually mounted /dev/sda3 to /mnt and looked around - everything looks good. I umounted /mnt and manually ran fsck -t ext3 /dev/sda3 again, it was clean. Still, when the system is booted, the above messages appear. Also, I've used both the /dev/sdax aliases and the /dev/disk/by-path/xxx full names in the fstab with the same result. inst-sys:/mnt/etc # cat fstab /dev/sda1 /boot ext3 acl,user_xattr 1 2 /dev/sda2 swapswap defaults0 0 /dev/sda3 / ext3 acl,user_xattr 1 1 #/dev/disk/by-path/ccw-0.0.d000-zfcp-0x5006048ad52cea89:0x0701-part2 swap swap defaults 0 0 #/dev/disk/by-path/ccw-0.0.d000-zfcp-0x5006048ad52cea89:0x0701-part3 /ext3 acl,user_xattr1 1 #/dev/disk/by-path/ccw-0.0.d000-zfcp-0x5006048ad52cea89:0x0701-part1 /bootext3 acl,user_xattr1 2 Looking for ideas on what to look at next. Thanks, Joe -- 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
Re: SLES11 boot problem
I did catch the error in the fstab and put the mount for /boot after the mount for /. On Mon, Jan 11, 2010 at 2:57 PM, Joe Martin widet.jmar...@gmail.com wrote: Have a VM guest running SLES 11 - has been working fine for months - rebooted several times. Over the weekend there was a problem with the SAN switch and the guest lost it's paths to disk. Now when we try to boot the guest, we see the following. Waiting for device /dev/sda3 to appear: ok fsck 1.41.1 (01-Sep-2008) [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda3 fsck.ext3: Device or resource busy while trying to open /dev/sda3 Filesystem mounted or opened exclusively by another program? fsck failed. Mounting root device read-only. Mounting root /dev/sda3 mount -o ro,acl,user_xattr -t ext3 /dev/sda3 /root mount: /dev/sda3 already mounted or /root busy could not mount root filesystem -- exiting to /bin/sh We've booted the guest in repair mode. I initially used the Repair Installed System tool to repair the file system and it came back clean. I then logged onto the system using ssh and manually mounted /dev/sda3 to /mnt and looked around - everything looks good. I umounted /mnt and manually ran fsck -t ext3 /dev/sda3 again, it was clean. Still, when the system is booted, the above messages appear. Also, I've used both the /dev/sdax aliases and the /dev/disk/by-path/xxx full names in the fstab with the same result. inst-sys:/mnt/etc # cat fstab /dev/sda1 /boot ext3 acl,user_xattr 1 2 /dev/sda2 swapswap defaults0 0 /dev/sda3 / ext3 acl,user_xattr 1 1 #/dev/disk/by-path/ccw-0.0.d000-zfcp-0x5006048ad52cea89:0x0701-part2 swap swap defaults 0 0 #/dev/disk/by-path/ccw-0.0.d000-zfcp-0x5006048ad52cea89:0x0701-part3 /ext3 acl,user_xattr1 1 #/dev/disk/by-path/ccw-0.0.d000-zfcp-0x5006048ad52cea89:0x0701-part1 /bootext3 acl,user_xattr1 2 Looking for ideas on what to look at next. Thanks, Joe -- 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
