Re: DASD driver errors - sles 12 sp2 current maintenance

Thanks! That's worth a shot. I'll have to do some experimenting. SLES 11 never had any issues with it and LVM certainly shouldn't lose its wits until the next reboot, but if we can work around that, at least we can avoid getting it into that state and save a reboot. Marcy -Original

Re: DASD driver errors - sles 12 sp2 current maintenance

Thanks Stefan. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Stefan Haberland Sent: Tuesday, May 2, 2017 7:14 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] DASD driver errors - sles 12 sp2 current maintenance > I would open a ticket

Re: DASD driver errors - sles 12 sp2 current maintenance

On 02.05.2017 12:34, Stefan Haberland wrote: Hi Marcy, May 01 18:12:35 cdzea02a9919 kernel: dasd-eckd.b3193d: 0.0.8006: An error occurred in the DASD device driver, reason=09 May 01 18:12:35 cdzea02a9919 kernel: dasd(eckd): I/O status report for device 0.0.8006:

Re: DASD driver errors - sles 12 sp2 current maintenance

Hi Marcy, May 01 18:12:35 cdzea02a9919 kernel: dasd-eckd.b3193d: 0.0.8006: An error occurred in the DASD device driver, reason=09 May 01 18:12:35 cdzea02a9919 kernel: dasd(eckd): I/O status report for device 0.0.8006: dasd(eckd): in req: 7d437ed8

Re: DASD driver errors - sles 12 sp2 current maintenance

On Tuesday, 05/02/2017 at 10:48 GMT, Stefan Haberland wrote: > kernel: dasd(eckd): I/O status report for device 0.0.8006: > dasd(eckd): in req: 7d437ed8 CC:00 FC:04 AC:00 SC:17 DS:0E CS:00 RC:0 > dasd(eckd): device 0.0.8006: Failing CCW:

Re: Dump volumes made with zipl -d

On 05/01/2017 10:20 PM, Marcy Cortes wrote: Is my dump volume made with zipl -d on SLES 11 SP4 still good for SLES 12 SP2? Would be nice not to have 2 of them. There might be some differences regarding SMT (and maybe also SIMD) support but I'm not sure that's really all to take into account:

Re: DASD driver errors - sles 12 sp2 current maintenance

I would open a ticket so that that Linux doesn't issue it when using a non-fp minidisk (which it can easily find out). Error messages should never be treated as "oh, just ignore it." If you do that, then you ignore the real error messages. You are right and all I was saying was that the

Re: DASD driver errors - sles 12 sp2 current maintenance

>>> On 5/2/2017 at 06:44 AM, Stefan Haberland wrote: > Most likely someone from z/VM has to look at this. Doing a cat on the host_access_count file gets the same/similar error when running in an LPAR. So, I don't think this is necessarily z/VM related.

Re: DASD driver errors - sles 12 sp2 current maintenance

>>> On 5/1/2017 at 07:28 PM, Marcy Cortes >>> wrote: > So maybe LVM2 needs to hold off in SLES 12 SP2? How? > > And yes, its entirely possible the minidisk had stuff on it before which is > why we always dasdfmt first. I suppose you could try doing a