Hi Mark, I was afraid of that. There is a first for everything, this is the first time in 20+ years I have such problems with unsupported versions on new hardware. Up until last year we even ran VSE 2.2 in a z10. And we have always has older (unsupported) Linux systems on more recent hardware (SLES8/9 on z10).
Anyway. As you mention it might lead to data corruption, got it. But I can still read the files from those disks in a SLES11 machine. And we don't see similar problems with SLES10 SP2 (though perhaps we are just lucky). So a case of YMMV? And would this also affect ssh related issues as we've seen at the start of the problems? Is there any way to resolve it? Other than an emergency migration to SLES11 and hope for the best? (Luckily it's only one production system so the damage is not too big.) Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen, Berry van Sleeuwen -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Mark Post Sent: Wednesday, June 29, 2016 6:17 PM To: [email protected] Subject: Re: Unable to login with ssh >>> On 6/29/2016 at 05:42 AM, "van Sleeuwen, Berry" >>> <[email protected]> wrote: > A few months ago we have moved to a z13 and zVM 6.3. All machines were > moved successfully. But we now have problems with SLES10 SP4 machines. Ah, this is most likely the cause of your problem. Because SLES10 was EOL (and we don't have a z13), we didn't test it on a z13. IBM, however, has told us to expect problems with data corruption/loss in such an environment. Mark Post ---------------------------------------------------------------------- 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/ 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.
