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 http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
