Sent: Tuesday, November 18, 2014 10:50 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: device-mapper: reload ioctl on failed
I just realized that I was in a different situation that you are in. We had
multiple Linux users sharing a disk on an LVM R/O, but what you have is one R/W
and multiple R/O. I
:LINUX-390@VM.MARIST.EDU] On Behalf Of Shumate,
Scott
Sent: Tuesday, November 18, 2014 3:56 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: device-mapper: reload ioctl on failed
Thanks for the reply Thomas. I'm going to pass this on to our Linux guys, this
is their arena. I'm trying to hel
ux side. Works fine in our QA
environment. Just fails on our test environment.
Thanks
Scott
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Pavelka,
Tomas
Sent: Tuesday, November 18, 2014 2:27 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: device-
.
Thanks
Scott
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Scott
Rohling
Sent: Sunday, November 16, 2014 10:56 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: device-mapper: reload ioctl on failed
Hmm.. what's providing the sharing of the u
> It works if I attach the mini-disk was multi-write. This is not what we want
> but it works. Any ideas?
A lot of speculation on my part follows. Again I will point to Red Hat as the
more informed party. The bug I dealt with before seems very similar to what you
are experiencing. There were
ssage-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
> Scott Rohling
> Sent: Friday, November 14, 2014 10:55 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: device-mapper: reload ioctl on failed
>
> Need to reword after 'It works if...' n
Sent: Friday, November 14, 2014 10:55 AM
To: LINUX-390@VM.MARIST.EDU
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
r.
>
> BR /Tore Agblad Volvo IT
>
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
> Shumate, Scott
> Sent: den 14 november 2014 3:53
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: device-mapper: reload ioctl on failed
&g
Sent: Friday, November 14, 2014 3:48 AM
To: LINUX-390@VM.MARIST.EDU
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
] On Behalf Of Shumate,
Scott
Sent: den 14 november 2014 3:53
To: LINUX-390@VM.MARIST.EDU
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
Behalf Of Dan Horák
Sent: Thursday, November 13, 2014 11:43 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: device-mapper: reload ioctl on failed
On Thu, 13 Nov 2014 15:58:42 +
"Pavelka, Tomas" wrote:
> > lvm2-2.02.100-8.el6.s390x
>
> When I was dealing with this I had a ve
er 13, 2014 10:59 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: device-mapper: reload ioctl on failed
> 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
proble
On Thu, 13 Nov 2014 15:58:42 +
"Pavelka, Tomas" 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 th
> 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.
Tomas
|grep lvm
lvm2-2.02.88-12.el5
system-config-lvm-1.1.5-14.el5
Thanks
Scott
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Pavelka,
Tomas
Sent: Thursday, November 13, 2014 3:45 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: device-mapper: reload ioctl
On Thu, 13 Nov 2014 08:45:02 +
"Pavelka, Tomas" wrote:
> What version of the lvm RPM are you running? We have run into a
or what version of RHEL6 are you installing? Looking into the history
of the lvm2 package it might have been already fixed in one of the
latest updates.
What version of the lvm RPM are you running? We have run into a problem on a
CentOS 6 installation where LVM would not put online disks that were read only.
The bug started at a version that I unfortunately forgot and was fixed in a
newer version that I forgot as well. But I managed to find one
, 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
O
t; 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: In
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 getti
20 matches
Mail list logo
