They are causing the volumes unusable on the server.  To my point, the same 
disk can be mounted successfully  s r/o and usable on the old RHEL5 servers.

Thanks
Scott


-----Original Message-----
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Scott 
Rohling
Sent: Wednesday, November 12, 2014 3:27 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: device-mapper: reload ioctl on failed

I'm not sure -- but am wondering if the errors prevent the volume group
from being used?   Are these just informational or are they causing the
volumes to be unusable?

Scott Rohling

On Wed, Nov 12, 2014 at 12:09 PM, Shumate, Scott <scshum...@bbandt.com>
wrote:

> Hi everyone,
>
> I'm running into an interesting situation that I have not seen before.
> We currently have an environment running RHEL5 servers.  One of the
> servers have a set of mini-disk mounted r/w (703 thru 706) and other
> RHEL5 servers mounted r/o (703 thru 706).  It works great.
>
> The problem we are running into is we have created new RHEL6 servers.
> We are trying to attach to the same mini-disk (703 thru 706) to these
> servers as r/o.  I can successfully attach the disk to the guest as
> read-only and do chccwdev to get them online.
>
> We do a vgscan --ignorelockingfailure
> Then we do a vgchange -a y --ignorelockingfailure VolGroup01
>
> We get the following error:
>
> 2 logical volume(s) in volume group "VolGroup01" now active
>   device-mapper: reload ioctl on  failed: Invalid argument
>   device-mapper: reload ioctl on  failed: Invalid argument
>
> Any ideas why we are getting these errors?
>
> Thanks
> Scott
>
>
>
> 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 
lists...@vm.marist.edu 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 lists...@vm.marist.edu 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/

Reply via email to