Re: Getting 'incorrect semaphore state' on self configured server kernel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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/

_______________________________________________
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/


[Index of Archives]     [Gluster Users]     [Kernel Development]     [Linux Clusters]     [Device Mapper]     [Security]     [Bugtraq]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]

  Powered by Linux