I'm just supposing here, that you put and it's on a test bed server first, at which point you would have found the problem with the xfs file system and been able to back it out. Only after maintenance has been thoroughly vetted on the test bed server wood shove it down the throats of the other servers.
But, I never was responsible for Linux on Z systems servers, so I may have missed out on all the fun. Mike Walter -Retired- ________________________________ From: Linux on 390 Port <[email protected]> on behalf of Marcy Cortes <[email protected]> Sent: Thursday, May 24, 2018 11:00:12 AM To: [email protected] Subject: Re: Bug with XFS and SLES 12SP3 kernel-default-4.4.131-94.29-default Nice idea, but when you have a thousand servers, that isn't very practical. And one your server has been up a few minutes its data has changed and regressing it that way may be a problem. The multi kernel support works well for things like backing out the kernel. -----Original Message----- From: Linux on 390 Port <[email protected]> On Behalf Of John McKown Sent: Thursday, May 24, 2018 7:51 AM To: [email protected] Subject: Re: [LINUX-390] Bug with XFS and SLES 12SP3 kernel-default-4.4.131-94.29-default On Thu, May 24, 2018 at 9:29 AM Mike Walter <[email protected]> wrote: > When I was a young man learning the art of systems programming sooo > long ago, I was taught that the first step of applying maintenance is > to make a physical backup of the target volumes. That way you have a > validated source with which to return if/when the maintenance fails. Just > sayin'. > :-) > Total agreement. I'm having a problem with a sandox system right now with some maintenance (but it's z/OS, not Linux). But that's what I did -- physical back of all the volumes before doing _anything_. I do the same sort of thing when I install a never version of a product. I do a "tar" backup of the various files (it they're in /etc or /var or ...) & filesystems. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=02%7C01%7C%7C74815a2d96a04a6abef508d5c18fc160%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636627745517533603&sdata=T6se4MfGCrQKhEoLAl1GSZdahtAXs2ZZd4gZiuAwgjU%3D&reserved=0 ---------------------------------------------------------------------- For more information on Linux on System z, visit https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.linuxvm.org%2F&data=02%7C01%7C%7C74815a2d96a04a6abef508d5c18fc160%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636627745517533603&sdata=84ePrZlYwZTFJpCrEaMBxk9u2g%2FiN1kja9rARzKuHl0%3D&reserved=0 ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
