[linux-lvm] Getting 'incorrect semaphore state' on self configured server kernel

[linux-lvm] Getting 'incorrect semaphore state' on self configured server kernel

[Mark van Dijk]

Hello,

When I run lvcreate and lvremove I get the errors you can see at the
bottom of this email. I have been seeing this on kernels I configured
from scratch, right now this is version 3.5 on an x64 running ArchLinux.

I must have made a mistake with the kernel's options or I am
overlooking something. It's clearly a configuration option because I
don't get these errors with ArchLinux's distribution kernel. So what am
I doing wrong?

Note, LVM does work fine apart from these issues.

After many compiling iterations I'm all out of ideas and while I'm
aware that one can work around the errors LV's with the -Zn options,
I'd rather get this stuff fixed :)

This is my kernel config: http://pastebin.com/isVsziSe

The error:

# lvcreate -L100M -n foobar -v array 
/dev/array/foobar: not found: device not cleared
Aborting. Failed to wipe start of new LV.
semid 983040: semop failed for cookie 0xd4d19ee: incorrect semaphore
state Failed to set a proper state for notification semaphore
identified by cookie value 223156718 (0xd4d19ee) to initialize waiting
for incoming notifications.

I appreciate all help I can get.

-- 
Kind regards,
Mark van Dijk.                  ,-----------------------------------
-------------------------------'           Tue Aug 07 12:00 UTC 2012
Today is Prickle-Prickle, the 73rd day of Confusion in the YOLD 3178

Re: [linux-lvm] Getting 'incorrect semaphore state' on self configured server kernel

[Mark van Dijk]

> # lvcreate -L100M -n foobar -v array 
> /dev/array/foobar: not found: device not cleared
> Aborting. Failed to wipe start of new LV.
> semid 983040: semop failed for cookie 0xd4d19ee: incorrect semaphore
> state Failed to set a proper state for notification semaphore
> identified by cookie value 223156718 (0xd4d19ee) to initialize waiting
> for incoming notifications.
> 
> I appreciate all help I can get.
> 

I still haven't solved this.. who is willing to lend me a hand please?

Re: [linux-lvm] Getting 'incorrect semaphore state' on self configured server kernel

[Scott Merrilees]

A diff -u of a working kernel config vs a non-working config would
possibly help.
--
Scott Merrilees


On Sun, Aug 12, 2012 at 11:33 PM, Mark van Dijk
<lists+linux-lvm@internecto.net> wrote:
>> # lvcreate -L100M -n foobar -v array
>> /dev/array/foobar: not found: device not cleared
>> Aborting. Failed to wipe start of new LV.
>> semid 983040: semop failed for cookie 0xd4d19ee: incorrect semaphore
>> state Failed to set a proper state for notification semaphore
>> identified by cookie value 223156718 (0xd4d19ee) to initialize waiting
>> for incoming notifications.
>>
>> I appreciate all help I can get.
>>
>
> I still haven't solved this.. who is willing to lend me a hand please?
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

Re: [linux-lvm] Getting 'incorrect semaphore state' on self configured server kernel

[Mark van Dijk]

> >>> # lvcreate -L100M -n foobar -v array 
> >>> /dev/array/foobar: not found: device not cleared
> >>> Aborting. Failed to wipe start of new LV.
> >>> semid 983040: semop failed for cookie 0xd4d19ee: incorrect
> >>> semaphore state Failed to set a proper state for notification
> >>> semaphore identified by cookie value 223156718 (0xd4d19ee) to
> >>> initialize waiting for incoming notifications.
> >> 
> >> I appreciate all help I can get.
> >> 
> >
> > I still haven't solved this.. who is willing to lend me a hand
> > please?
>
> A diff -u of a working kernel config vs a non-working config would
> possibly help.
> --
> Scott Merrilees

(I'm replying to a digest so sorry if the formatting is a bit off. I
disabled digests for now.)

Scott, thanks for your suggestion. I followed it, changed more settings
just for testing, and still can't get it to work without these errors.

So I tried to build a kernel, same version and same config on a
different distribution, this time I chose AlpineLinux. And lo, the
errors are not occurring there.

This makes me suspicious about Archlinux's udev version and/or methods,
but the question about why their own kernel doesn't have these issues
remains.

What to try next? Where to look?

-- 
Stay in touch,
Mark van Dijk.                  ,------------------------------------
-------------------------------'            Sun Aug 12 15:21 UTC 2012
Today is Prickle-Prickle, the 5th day of Bureaucracy in the YOLD 3178
Celebrate Zaraday

Re: [linux-lvm] Getting 'incorrect semaphore state' on self configured server kernel

[Zdenek Kabelac]

Dne 12.8.2012 17:31, Mark van Dijk napsal(a):
>>>>> # lvcreate -L100M -n foobar -v array
>>>>> /dev/array/foobar: not found: device not cleared
>>>>> Aborting. Failed to wipe start of new LV.
>>>>> semid 983040: semop failed for cookie 0xd4d19ee: incorrect
>>>>> semaphore state Failed to set a proper state for notification
>>>>> semaphore identified by cookie value 223156718 (0xd4d19ee) to
>>>>> initialize waiting for incoming notifications.
>>>>
>>>> I appreciate all help I can get.
>>>>
>>>
>>> I still haven't solved this.. who is willing to lend me a hand
>>> please?
>>
>> A diff -u of a working kernel config vs a non-working config would
>> possibly help.
>> --
>> Scott Merrilees
>
> (I'm replying to a digest so sorry if the formatting is a bit off. I
> disabled digests for now.)
>
> Scott, thanks for your suggestion. I followed it, changed more settings
> just for testing, and still can't get it to work without these errors.
>
> So I tried to build a kernel, same version and same config on a
> different distribution, this time I chose AlpineLinux. And lo, the
> errors are not occurring there.
>
> This makes me suspicious about Archlinux's udev version and/or methods,
> but the question about why their own kernel doesn't have these issues
> remains.
>
> What to try next? Where to look?
>

Check you are not having set   CONFIG_UEVENT_HELPER_PATH in your kernel
(or preset on your system) - If I remember, there was a one Archlinux user
with very old kernel .config file which was just updated.

On modern udev based distro you should let udev to handle uevents.

Zdenek