Yes I agree. Its shared binaries used to apply maintenance. We don't want it this way that is why we are trying to figure out why the linux os can't mount them r/o. The only way we can get it to work is link the disk mw then turn around and mount them r/o on the linux os. That is the only way the linux OS can mount them r/o.
To make things even weirder, I can use another RHEL5 server and link it r/o and mount the file system r/o on the same RHEL6 server. Make me think there is something different in the RHEL5 server and not the RHEL6 server, but I can't see it. Thanks Scott -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Scott Rohling Sent: Sunday, November 16, 2014 10:56 PM To: [email protected] Subject: Re: device-mapper: reload ioctl on failed Hmm.. what's providing the sharing of the underlying filesystem? LINK MW allows more then one guest to link read/write... when you attach, then it's not a minidisk any more, and only the guest that attached it can use it. MW usually isn't recommended unless there is some kind of reserve/release to ensure only one guest writes at a time.. (MWV provides virtual reserve/release for fullpack minidisks). What's running on these guests (middleware/application) and using these disks? What you're showing looks dangerous.. Scott Rohling On Sun, Nov 16, 2014 at 3:50 PM, Shumate, Scott <[email protected]> wrote: > It's a shared mini-disk. > > LINK LXD20069 0707 0707 MW > LINK LXD20069 0708 0708 MW > LINK LXD20069 0709 0709 MW > LINK LXD20069 070A 070A MW > > Sorry for the confusion. > > Thanks > Scott > > > -----Original Message----- > From: Linux on 390 Port [mailto:[email protected]] On Behalf Of > Scott Rohling > Sent: Friday, November 14, 2014 10:55 AM > To: [email protected] > Subject: Re: device-mapper: reload ioctl on failed > > Need to reword after 'It works if...' not sure what you are saying.. > are these fullpack minidisks? Did you have them linked as MW or MWV > before? ATTACH doesn't allow multiwrite... It is no longer a minidisk > available to the system because the volume is attached to your guest. > > But please re - explain -- :-) A directory entry showing the MDISKs > might help too.. i'm not clear on your disk setup.. > > Scott Rohling > > On Fri, Nov 14, 2014 at 7:46 AM, Shumate, Scott <[email protected]> > wrote: > > > We have it in the new servers. I have another interesting fact. It > > works if I attach the mini-disk was multi-write. This is not what > > we want but it works. Any ideas? > > > > Thanks > > Scott > > > > > > -----Original Message----- > > From: Linux on 390 Port [mailto:[email protected]] On Behalf > > Of Agblad Tore > > Sent: Friday, November 14, 2014 3:48 AM > > To: [email protected] > > Subject: Re: device-mapper: reload ioctl on failed > > > > You might have mismatch in zipl.conf, missing some disks that is > > used by root lvm. > > All disks used in a lvm for / must be specified in zipl.conf. > > I spent some hours finding that error. > > > > BR /Tore Agblad Volvo IT > > > > -----Original Message----- > > From: Linux on 390 Port [mailto:[email protected]] On Behalf > > Of Shumate, Scott > > Sent: den 14 november 2014 3:53 > > To: [email protected] > > Subject: Re: device-mapper: reload ioctl on failed > > > > More errors: > > > > device-mapper: table: 253:18: linear: dm-linear: Device lookup > > failed > > device-mapper: ioctl: error adding target to table > > device-mapper: table: 253:19: linear: dm-linear: Device lookup > > failed > > device-mapper: ioctl: error adding target to table > > device-mapper: table: 253:1: linear: dm-linear: Device lookup failed > > device-mapper: ioctl: error adding target to table > > device-mapper: table: 253:2: linear: dm-linear: Device lookup failed > > device-mapper: ioctl: error adding target to table > > > > Thanks > > Scott > > > > -----Original Message----- > > From: Linux on 390 Port [mailto:[email protected]] On Behalf > > Of Dan Horák > > Sent: Thursday, November 13, 2014 11:43 AM > > To: [email protected] > > Subject: Re: device-mapper: reload ioctl on failed > > > > On Thu, 13 Nov 2014 15:58:42 +0000 > > "Pavelka, Tomas" <[email protected]> wrote: > > > > > > lvm2-2.02.100-8.el6.s390x > > > > > > When I was dealing with this I had a version that had the bug > > > fixed and I think it was older than 2.02.100. It was 2.02.9x > > > something. I would guess that your problem is LVM related but not > > > the same that I had. Red Hat would give you better advice than I do. > > > > yes, Scott, please open a support request, the support guys will ask > > for sosreport and I think appending a strace output for the lvchange > > call would be also helpful > > > > > > Dan > > > > -------------------------------------------------------------------- > > -- 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/ > > > > > > The information in this transmission may contain proprietary and > > non-public information of BB&T or its affiliates and may be subject > > to protection under the law. The message is intended for the sole > > use of the individual or entity to which it is addressed. If you are > > not the intended recipient, you are notified that any use, > > distribution or copying of the message is strictly prohibited. If > > you received this message in error, please delete the material from > > your system without reading the content and notify the sender > > immediately of the inadvertent > transmission. > > > > -------------------------------------------------------------------- > > -- 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/ > > > > -------------------------------------------------------------------- > > -- 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/ > > > > -------------------------------------------------------------------- > > -- 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/ > > > > ---------------------------------------------------------------------- > 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/ > > > The information in this transmission may contain proprietary and > non-public information of BB&T or its affiliates and may be subject to > protection under the law. The message is intended for the sole use of > the individual or entity to which it is addressed. If you are not the > intended recipient, you are notified that any use, distribution or > copying of the message is strictly prohibited. If you received this > message in error, please delete the material from your system without > reading the content and notify the sender immediately of the inadvertent > transmission. > > ---------------------------------------------------------------------- > 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/ > ---------------------------------------------------------------------- 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/ The information in this transmission may contain proprietary and non-public information of BB&T or its affiliates and may be subject to protection under the law. The message is intended for the sole use of the individual or entity to which it is addressed. If you are not the intended recipient, you are notified that any use, distribution or copying of the message is strictly prohibited. If you received this message in error, please delete the material from your system without reading the content and notify the sender immediately of the inadvertent transmission. ---------------------------------------------------------------------- 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/
