Over the weekend, my Slack/390 system fell back an hour for daylight savings time. How do I adjust when this happens? I think it's supposed to happen next week.
Russell Jones ANPAC -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Hall, Ken (GTS) Sent: Monday, October 27, 2008 11:23 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Zfcp.conf No, it's not necessary, if everything has been done properly. It has to do with when in the boot process the FCP devices are attached. If you ALLOW mkinitrd to put zfcp.conf in the initrd, those disks will be attached before the root filesystem is mounted. If you're okay with that, then it's fine. But if you want more flexibility, it might make more sense to remove zfcp.conf entirely before running mkinitrd. That way, NO FCP disks are attached before the root filesystem mounts, so it's all handled later in the boot process, and it all still works. There are a couple of gotchas with this. In versions prior to RHEL5.2, zfcpconf.sh was run out of /etc/rc.s/rc.sysinit. This resulted in a "chicken-egg" situation when multipath and/or LVM were used, and Red Hat went through several iterations trying to fix it, going all the way back to RHEL4.4. 5.2 triggers the script out of udev, which also nicely solves a race condition in rc.sysinit, where udev doesn't build the device nodes fast enough for LVM to catch them. Far as multipath goes, I don't see why changing the WWPN and Bus ID should have changed the identifier that's stored in the bindings file, but it's possible, since I forget how that's calculated. The simplest way to straighten it all out is to run "multipath -F", remove all entries from the bindings file, and then run "multipath", and let them rebuild. You might have to check to be sure you're mounting filesystems on the right places, though, if you're mounting by node. We're planning to standardize on either using LVM, or mount by label, to avoid this. Two other quick hints: The default location for the bindings file is in /var/lib. If /var is on a separate filesystem from root, the bindings file will be built in the wrong place, or not built at all, and /var will be mounted over it. The latest versions of device-mapper-multipath have a parameter in /etc/multipath.conf that allows you to specify the location of the bindings file. Earlier versions required it to be changed via command line parm, which, of course, required you do surgery on the init script. Finally, the version of mount that comes with RHEL5.2 uses a new scheme to prioritize mounts so that multipath devices and their components don't look like the same disk. This used to cause mount-by-label to fail. If you start getting mount failures, "device busy", or "duplicate device" messages, check file /etc/blkid/blkid.tab. If you've added and removed LUNs, this file can contain residual data that confuses mount. Just delete it, and reboot, it will be rebuilt properly. Good luck! -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Romanowski, John (OFT) Sent: Monday, October 27, 2008 11:31 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Zfcp.conf I don't actually have any Redhats myself but an IBM manual said after changing Redhat's zfcp.conf it's necessary to re-run mkinitrd and zipl to make the zfcp.conf changes survive (take effect) at reboot. Given that and you said " After the reboot, the original paths were still being used.", I suspect the initrd's got the prior contents of zipl.conf built into it and doesn't know yet about your changes to the zfcp.conf file. > -------------------------------------------------------- This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Spann, Elizebeth (Betsie) > Sent: Monday, October 27, 2008 11:21 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Zfcp.conf > > Duh, no. I'll try it. Is this a guess or have you been successful? > Thanks, > Betsie > > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Romanowski, John (OFT) > Sent: Friday, October 24, 2008 7:38 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Zfcp.conf > > Betsie, > After changing zfcp.conf did you run mkinitrd and zipl before rebooting? > > > > -------------------------------------------------------- > This e-mail, including any attachments, may be confidential, privileged > or otherwise legally protected. It is intended only for the addressee. > If you received this e-mail in error or from someone who was not > authorized to send it to you, do not disseminate, copy or otherwise use > this e-mail or its attachments. Please notify the sender immediately by > reply e-mail and delete the e-mail from your system. > > > -----Original Message----- > > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > > Spann, Elizebeth (Betsie) > > Sent: Friday, October 24, 2008 7:29 PM > > To: LINUX-390@VM.MARIST.EDU > > Subject: Zfcp.conf > > > > Hi, > > I changed my zfcp.conf file and rebooted. I did not erase the > > multipath_bindings file. > > RHEL 5. device-mapper-multipath-0.4.7-17.el5 > > My multipath.conf is configured to use multipath_bindings file > > > > I left the LUNs in the same order but changed zfcp.conf fields 1 and > 3; > > i.e. the FCP device and the WWPN. > > After the reboot, the original paths were still being used. I checked > > > this with multipath -ll and lsscsi. > > All the hosts are listed with lszfcp but not all are in multipath -ll. > > > > Can the LUN order in zfcp.conf be changed if I retain the same > > multipath_bindings file? I don't understand how the two files are > > related. > > I thought the multipath_bindings file preserved the mpathxx assignment > > > to the devices. > > I thought the zfcp.conf file assigned LUNs to FCP routes. > > > > Betsie > > > > ---------------------------------------------------------------------- > > 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 ---------------------------------------------------------------------- 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 -------------------------------------------------------- This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -------------------------------------------------------- ---------------------------------------------------------------------- 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
