[no subject]
>>> On 6/10/2015 at 09:51 PM, Mainframe Mainframe >>> wrote: > From z/VM console and I am not good at using SID editor commands. Can > anybody provide syntax for changing this line using SID editor commands. What is "SID?" 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
[no subject]
Hello , Thanks for reply .As I mentioned, fsck is running on rebooting time and its not getting completed and having issue mentioned earlier email chain. So, to isolate this issue, I want to revert back dev/sda1/scratch ext3 defaults 1 2 to /dev/sda1/scratch ext3 defaults 1 0 under /etc/fstab >From z/VM console and I am not good at using SID editor commands. Can anybody provide syntax for changing this line using SID editor commands. Currently system is accessible in repair filesystem mode. (Repair filesystem) 1 # On Tue, Jun 9, 2015 at 2:31 PM, Steffen Maier wrote: > On 06/09/2015 09:22 AM, Mainframe Mainframe wrote: > >> Hello Group, >>Currently we facing below issue. >> >> *Issue : * >> >> /scratch is on dasda1 device. We need mount sda device on /scratch so that >> we can do porting work. >> >> Steps taken to solve issue : >> >> # umount -l /scratch >> > > This seems to be a lazy unmount, so you don't know when this mount point > will be truely unmounted properly. > > # fsck -y /scratch >> fsck 1.39 (29-May-2006) >> e2fsck 1.39 (29-May-2006) >> fsck.ext3: Attempt to read block from filesystem resulted in short read >> while trying to open /dev/sda1 >> Could this be a zero-length partition? >> > > Maybe due to the lazy unmount, /scratch might be in some intermediate > state or now even already belong to containing the root-fs(!), so calling > fsck on that mount point seems dangerous. > > A safe procedure might be to unmount without lazy option and then fsck the > block device that used to be mounted on /scratch, i.e. /dev/dasda1. > > *cat /etc/fstab* >> >> LABEL=/ / ext3 >> defaults,usrquota,grpquota1 1 >> tmpfs /dev/shmtmpfs size=8045M >> 0 >> 0 >> devpts /dev/ptsdevpts gid=5,mode=620 0 >> 0 >> sysfs /syssysfs defaults0 >> 0 >> proc/proc procdefaults0 >> 0 >> /dev/sda1/scratch ext3 defaults 1 0 >> >> >> *We changed * >> >> /dev/sda1/scratch ext3 defaults 1 0 >> >> to >> >> /dev/sda1/scratch ext3 defaults 1 2 >> > > You should always use multipathing instead of single path SCSI devices, > otherwise you lack path redundancy. > > How do you ensure that all the paths to this SCSI disk are persistently > configured? > (SCSI devices don't appear fully automatically without any user action > with Linux on z Systems.) > In other words, it could have been that there is no /dev/sda at all during > fsck time on boot. > > > http://www-05.ibm.com/de/events/linux-on-z/pdf/day2/4_Steffen_Maier_zfcp-best-practices-2015.pdf > > *So, that fsck run on reboot time and we rebooted system and after reboot >> I was getting below messages.* >> >> >> >> >> Checking all file systems. >> -/sbin/fsck.ext3 (1) -- /- fsck.ext3 -a /dev/dasda1 >> /: clean, 177325/5412928 files, 1517520/5408976 blocks >> -/sbin/fsck.ext3 (1) -- /scratch- fsck.ext3 -a /dev/sda1 >> fsck.ext3: No such file or directory while trying to open /dev/sda1 >> /dev/sda1: >> The superblock could not be read or does not describe a correct ext2 >> filesystem. If the device is valid and it really contains an ext2 >> filesystem (and not swap or ufs or something else), then the superblock >> is corrupt, and you might try running e2fsck with an alternate superblock: >> e2fsck -b 8193 >> >> -FAILED- >> >> *** An error occurred during the file system check. >> *** Dropping you to a shell; the system will reboot >> *** when you leave the shell. >> Give root password for maintenance >> >> >> e2fsck -b 8193 >> Usage: e2fsck --panyrcdfvstDFSV- --b superblock- --B blocksize- >> --I inode_buffer_blocks- --P process_inode_size- >> --l|-L bad_blocks_file- --C fd- --j external_journal- >> --E extended-options- device >> >> Emergency help: >> -p Automatic repair (no questions) >> -n Make no changes to the filesystem >> -y Assume "yes" to all questions >> -c Check for bad blocks and add them to the badblock >> list >> -f Force checking even if filesystem is marked clean >> -v Be verbose >> -b superblockUse alternative superblock >> -B blocksize Force blocksize when looking for superblock >> -j external_journal Set location of the external journal >> -l bad_blocks_file Add to badblocks list >> -L bad_blocks_file Set badblocks list >> (Repair filesystem) 2 # >> >> >> Any solution of this issue. >> > > -- > Mit freundlichen Grüßen / Kind regards > Steffen Maier > > Linux on System z Development > > IBM Deutschland Research & Development GmbH > Vorsitzende des Aufsichtsrats: Martina Koederitz > Geschaeftsfuehrung: Dirk Wittkopp > Sitz der Gesellschaft: Boeblingen > Registergericht:
Re: PAV z/VM and LINUX s390x (SUSE) question
Got it.. Thanks On Wed, Jun 10, 2015 at 12:00 PM, Mark Post wrote: > >>> On 6/10/2015 at 02:08 PM, Tom Huegel wrote: > > Hi all. > > This should be a simple question for someone who has done it before. > > How do I get z/LINUX to recognize and use pav alias volumes? > > You mean like this? > # lsdasd > Bus-ID Status Name Device Type BlkSz Size Blocks > > == > 0.0.27e0 alias ECKD > 0.0.0160 active dasda 94:0DIAG 51297MB 20 > 0.0.2601 active dasdb 94:4ECKD 4096 7043MB1803060 > > > I have the volumes defined, they are attached to the LINUX system > > everything shows up when I do Q PAV.. > > > > What am I missing? > > Do you have both a base volume _and_ an alias from the same pool attached > to the Linux guest? Are they both online from the Linux perspective? > > > 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 more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- 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: PAV z/VM and LINUX s390x (SUSE) question
>>> On 6/10/2015 at 02:08 PM, Tom Huegel wrote: > Hi all. > This should be a simple question for someone who has done it before. > How do I get z/LINUX to recognize and use pav alias volumes? You mean like this? # lsdasd Bus-ID Status Name Device Type BlkSz Size Blocks == 0.0.27e0 alias ECKD 0.0.0160 active dasda 94:0DIAG 51297MB 20 0.0.2601 active dasdb 94:4ECKD 4096 7043MB1803060 > I have the volumes defined, they are attached to the LINUX system > everything shows up when I do Q PAV.. > > What am I missing? Do you have both a base volume _and_ an alias from the same pool attached to the Linux guest? Are they both online from the Linux perspective? 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
PAV z/VM and LINUX s390x (SUSE) question
Hi all. This should be a simple question for someone who has done it before. How do I get z/LINUX to recognize and use pav alias volumes? I have the volumes defined, they are attached to the LINUX system everything shows up when I do Q PAV.. What am I missing? Thanks Tom -- 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: Problems with SCSI-over-FCP after machine upgrade
We have fixed this problem but made more than one change so we do not know the cause - it would be nice to know who to blame ! Thanks for all the advice. I followed up Scott's suggestion of creating an exec to delete the EDEV' s paths and to do SET EDEV CLEAR so that I could vary the CHPIDs offline. (I found that to redefine the EDEVs I had to use 'SET EDEV ' providing the Type, Attributes, FCP_dev, wwpn and LUN without the text 'ADD PATH' for the first path and with the text 'add path' for the other paths). There is no zoning or LUN masking involved and the NPIV wwpns had not changed (the physical NPIVs had changed - they contains the new PCHIPID ids). We had already tried switching everything in the paths off/on. The changes which we made to resolve the problem were: - switch firmware was upgraded from 6.1.1a to 6.3.0d . Neither had been qualified for zBC12. (We later upgraded to 7.0.0d)- removed the link between the two SAN switches. The SAN Volume Controller documentation says that the fibre networks should be independent. When I disconnected the link I found that one of the SFPs came out too - it had not 'clicked' into place.- cleaned the z12 end of the fibre links. All of the zlinuxes then came up and stayed up, except for some which relied on the ISL being in place. ie the LOADDEV parameters (for loading from chpid 18) specified an SVC wwpn which was now accessible only from the other CHPID, which was easily fixed. Maybe the problem was due to FCP channel microcode in z12 (or z114/196). Or maybe there were some fabric errors which were exacerbated by the faster z12 IFLs. Keith On Monday, 8 June 2015, 15:39, Raymond Higgs wrote: Hi Keith, Please check zoning and lun masking. I think the SVC management interface calls them hosts. If youdidn't do an MES upgrade, then the WWPNs of your channels changed. Regards, Ray Higgs System z FCP Firmware Development Bld. 706, B42 2455 South Road Poughkeepsie, NY 12601 (845) 435-8666, T/L 295-8666 rayhi...@us.ibm.com From: Keith Gooding To: LINUX-390@VM.MARIST.EDU Date: 06/04/2015 04:23 PM Subject: Problems withSCSI-over-FCP after machine upgrade Sent by: Linux on 390Port This may not be the proper forum but maybe someonecan help. We have a small number of linux systems (<32) under z/VM 6.3 whichuse SCSI connections to LUNs on a SAN Volume Controller via a couple ofIBM SAN24B switches (the equivalent of Brocade 300). There are also somesystems which use EDEVs on the same SVC. This had worked on z10 BC forabout 5 years without problems. Last week the z10 was upgraded to a zBC12, retaining the same FICON cards(4Gbs), but not necessarily associated with the same CHPIDs. Since thena number of the LUN connections have been 'lost', cauing linux systemsto fail. SCSIDISC displays eg "HCPRXS975I Virtual FCP device 1A05ignored because the adapter was not able to connect to the fibre channelnetwork". It is then not possible to rebot the linux system. Restarting 'everything' - ie SVC nodes, SAN switches, CHIPD vary off/on- cleared the problem for a while. Any ideas where to start looking ?. I have discovered that we have >32 FCP subchannels defined on the CHPID (but highest used unit addressis 1f, and there are only about a dozen in use). Also the switch has notbeen 'qualified' for use on z12 (but it appears that it was not qualifiedfor z10 either). Any advice greatly appreciated ! -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 orvisit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- 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: LNXMAINT vs LNXADMIN
Matt, I'd recommend keeping both of them. LNXMAINT is a CMS machine. It's main purpose is to have a R/W 192 disk that becomes the R/O 191 disk for all Linux virtual machines. In an SSI it is a USER as the disk can be shared among all members. LNXADMIN is a Linux machine. Many systems management solutions follow the model that there is one Linux per z/VM LPAR with additional privileges. In an SSI it is an IDENTITY because you want it running on each member LPAR. Then if your penguin herd grows, you'll be prepared. Hope this helps... -Mike MacIsaac On Wed, Jun 10, 2015 at 10:47 AM, Dazzo, Matt wrote: > Following the redbook install of zvm 6.3 and linux 6.4 install and they > describe these 2 servers (LNXMAINT, LNXADMIN). What are the major > differences between these 2 servers and do most of you create both and use > both? Could just 1 be used? Our environment here is going to be small, > maybe 1 or 2 servers. > > Thanks, > > Matt > > > -- > 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/ > -- 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/
LNXMAINT vs LNXADMIN
Following the redbook install of zvm 6.3 and linux 6.4 install and they describe these 2 servers (LNXMAINT, LNXADMIN). What are the major differences between these 2 servers and do most of you create both and use both? Could just 1 be used? Our environment here is going to be small, maybe 1 or 2 servers. Thanks, Matt -- 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: circular dependency pdat allocation
I will call Art Bell. Ran linux repair, rebuilt zipl, and recreated boot loader, it worked last night. But that doesn't explain why it worked ONCE after the DASD restore Anything that is not a mystery is just guesswork. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Alan Altmark Sent: Tuesday, June 09, 2015 9:36 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: circular dependency pdat allocation On Tuesday, 06/09/2015 at 09:27 EDT, "Dean, David (I/S)" wrote: > Anyway, I was then able to IPL this server 4 times successfully. > But the darned thing has been running for several years. I will see > at 3 AM > tonight. Sometimes the glue that hold the bits together into bytes gets brittle with age and some of the bits fall off. You have to glue them back on. Use a glue that remains flexible over a wide temperature range and pH. (What other explanation can there be? Sunspots? I don't think so, Tim..) -- Chuckie -- 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/ -- Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm -- 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: RHEL Install zvm
Thanks to those who responded, the issue was no vswitch defined. Moving on with the install until the next problem, thanks Matt -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: Friday, June 05, 2015 1:19 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: RHEL Install zvm >>> On 6/5/2015 at 01:15 PM, "Dazzo, Matt" wrote: > These are the only errors I have gotten so far. > > INFO kernel: dasda:CMS1/ LXM192: dasda1 > * NOTE: To enter default or empty values press enter twice. * > Device 0.0.0600 not present, trying to clear from blacklist and resense... > Device 0.0.0600 does not exist > Device 0.0.0601 not present, trying to clear from blacklist and resense... > Device 0.0.0601 does not exist > Device 0.0.0602 not present, trying to clear from blacklist and resense... > Device 0.0.0602 does not exist > 0) redo this parameter, 1) continue, 2) restart dialog, 3) halt, 4) shell And if you do a #CP Q NIC what comes back? What about #CP Q V ? 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 more information on Linux on System z, visit http://wiki.linuxvm.org/ -- 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/
