I have a newly installed SLES15 SP1 and in that machine I indeed noticed the udev rules were 41-* instead of 51-*. That includes both dasd-eckd and dasd-fba rules.
I don't know what an upgrade process would do with the existing rules. Usually we rebuild a machine instead of an upgrade in-place. Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen, Berry van Sleeuwen Flight Forum 3000 5657 EW Eindhoven -----Original Message----- From: Linux on 390 Port <[email protected]> On Behalf Of Aria Bamdad Sent: Friday, 20 August 2021 23:09 To: [email protected] Subject: Re: Warning if upgrading SLES12 to SLES15 SP3 Caution! External email. Do not open attachments or click links, unless this email comes from a known sender and you know the content is safe. Quoting Mark Post <[email protected]>: > On 8/19/21 6:17 PM, Aria Bamdad wrote: >> The upgrade to SP3 appears to >> cause a change in the udev definitions for the DASD defined on the >> server (in /etc/udev/rules.d) . For SLES 12 systems, these rules are >> 51-dasd-0.0.0xxx.rules files but it seems that for SLES15, they >> change format and number to 41-dasd-eckd-0.0.0xxx.rules. > > > This change actually happened with SLES12 SP4, when the chzdev and > lszdev tools were introduced to s390-tools by IBM. > > That's odd because none of my SLES 12 SP4 or SP5 systems have 41 rules. In fact none of my upgraded servers from 12 to 15 have them even for 15 SP1 or SP2. This happens at SP3 for me. >> However, this change does >> not happen for an upgraded SLES12 system to SLES15 until you upgrade >> to SLES15SP3. Once you upgrade to SP3, then the old 51-dasd rules >> are renamed with the '.legacy' extensions, new 41- rules are created. >> The rules for the vdisk for swap are left alone and thus after the >> upgrade, the swap partitions are no longer activated. There is more >> to this but I will not go into detail. > > Question, for each of the udev rules renamed to .legacy, is there an > equivalent 41-* rule present? > Only the eckd device rules were renamed from 51 to 51 with .legacy extension. Then new 41 rules defined for them. The FBA devices, namely the two vdisk swap disks were left alone with 51 rules and not 41 rules were defined. There are messages in the y2log file from mkinitrd stating it is skipping 51 rule devices. I have reported these to SUSE but they tech said she has no access to Z system so is testing on another architecture. I don't think that will help! Aria > > Mark Post > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO > LINUX-390 or visit > https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2. > marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=04%7C01%7CBerry.van > Sleeuwen%40atos.net%7C7e2bce5c23f94eef2ea408d9641ee507%7C33440fc6b7c74 > 12cbb730e70b0198d5a%7C0%7C0%7C637650906119697612%7CUnknown%7CTWFpbGZsb > 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D% > 7C1000&sdata=M%2FNsEkUC4m3PoK6tC%2BI4Nf3kXKMjay0pCNs87%2FQ1W64%3D& > amp;reserved=0 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=04%7C01%7CBerry.vanSleeuwen%40atos.net%7C7e2bce5c23f94eef2ea408d9641ee507%7C33440fc6b7c7412cbb730e70b0198d5a%7C0%7C0%7C637650906119707562%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=GvJI92wj3NbbAlv9G1bPyncBPiyoQFGni2PYf4MKEpQ%3D&reserved=0 This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, Atos’ liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. On all offers and agreements under which Atos Nederland B.V. supplies goods and/or services of whatever nature, the Terms of Delivery from Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly submitted to you on your request. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
