by-path is what we do I couldn't find any down side to it - unless you like to change virtual addresses in your VM directory entry randomly or something like that :)
Marcy "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Fargusson.Alan Sent: Tuesday, August 12, 2008 10:07 AM To: [email protected] Subject: Re: [LINUX-390] Safety Reminder: If you are planning disk upgrades, make sure you switch your Linux guests to by-path IDs in /etc/fstab BEFORE you switch Is there a consensus on what should be used? YAST gives me five choices. I don't understand some of them: Device name: I think this one is a problem if you add a device that has a lower device number then an existing device. Volume label: This might be a good way to go. This will probably break cloning. UUID: This might also be a good way to go, if UUIDs are really as unique as they should be. This probably will not work for cloning. Device ID: This one seems like a bad idea, since it breaks cloning, and it fails if one Linux instance has two or more minidisk on the same volume. Device path: This looks like the best option to me. Any down side to this? -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of David Boyes Sent: Tuesday, August 12, 2008 9:22 AM To: [email protected] Subject: Safety Reminder: If you are planning disk upgrades, make sure you switch your Linux guests to by-path IDs in /etc/fstab BEFORE you switch A safety reminder: If you're planning to replace disk subsystems, make sure your Linux guests (particularly any SLES 10 or above) guests do NOT use by-ID paths in /etc/fstab. Fix this BEFORE the new disk goes in, both RH and SuSE (Debian, too), or your guests will not be able to find their filesystems (and thus won't boot or run). This really should be in IBM and other DASD vendors planning information for new installs, and I'd demand a fix from your Linux vendors. By-ID is a stupid default for this architecture (for any architecture, I'd argue...) and needs a fix ASAP. IBM, EMC, Hitachi: how do we get this added to your planning guides? RH, Novell, how about it? -- db ---------------------------------------------------------------------- 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 ________________________________________________________________________ __________________________ CONFIDENTIALITY NOTICE: This email from the State of California is for the sole use of the intended recipient and may contain confidential and privileged information. Any unauthorized review or use, including disclosure or distribution, is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of this email. ---------------------------------------------------------------------- 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
