[gentoo-user] Internal error: Maps lock 14270464 < unlock 14274560

[gentoo-user] Internal error: Maps lock 14270464 < unlock 14274560

[Valmor de Almeida]

Hello,

After a recent new gentoo install on a lenovo laptop I get during booting:

Filesystem isclean
  * Remounting root filesystem read/write ...
  * Setting up the Logical Volume Manager ...
      Internal error: Maps lock 14270464 < unlock 14274560
      Internal error: Maps lock 14274560 < unlock 14278656
      Internal error: Maps lock 14278656 < unlock 14282752
      Internal error: Maps lock 14282752 < unlock 14286848
      Internal error: Maps lock 14286848 < unlock 14290944
  * Setting up dm-crypt mappings ...
[snip]
Filesystem is clean

I don't find other messages in /var/log/messages. Also the system seems 
to run fine. Has anyone seen these messages? Are they a false positive?

Thanks,

--
Valmor

Re: [gentoo-user] Internal error: Maps lock 14270464 < unlock 14274560

[Alex Schuster]

Valmor de Almeida writes:

> Filesystem isclean
>   * Remounting root filesystem read/write ...
>   * Setting up the Logical Volume Manager ...
>       Internal error: Maps lock 14270464 < unlock 14274560
>       Internal error: Maps lock 14274560 < unlock 14278656
>       Internal error: Maps lock 14278656 < unlock 14282752
>       Internal error: Maps lock 14282752 < unlock 14286848
>       Internal error: Maps lock 14286848 < unlock 14290944
>   * Setting up dm-crypt mappings ...
> [snip]
> Filesystem is clean
> 
> I don't find other messages in /var/log/messages. Also the system seems
> to run fine. Has anyone seen these messages? Are they a false positive?

I had similar errors when doing LVM stuff (while creating shapshots). They 
did no harm, and I found some bug report about it saying it's not a big 
problem, happing in some recent kernel. I'm running 2.6.35-tuxonice-r1 
now, and I no longer have them. But that might also have come from an 
update of lvm2.

	Wonko

Re: [gentoo-user] Internal error: Maps lock 14270464 < unlock 14274560

[Valmor de Almeida]

On 09/15/2010 07:40 AM, Alex Schuster wrote:
> Valmor de Almeida writes:
>
>> Filesystem isclean
>>    * Remounting root filesystem read/write ...
>>    * Setting up the Logical Volume Manager ...
>>        Internal error: Maps lock 14270464<  unlock 14274560
>>        Internal error: Maps lock 14274560<  unlock 14278656
>>        Internal error: Maps lock 14278656<  unlock 14282752
>>        Internal error: Maps lock 14282752<  unlock 14286848
>>        Internal error: Maps lock 14286848<  unlock 14290944
>>    * Setting up dm-crypt mappings ...
>> [snip]
>> Filesystem is clean
>>
>> I don't find other messages in /var/log/messages. Also the system seems
>> to run fine. Has anyone seen these messages? Are they a false positive?
>
> I had similar errors when doing LVM stuff (while creating shapshots). They
> did no harm, and I found some bug report about it saying it's not a big
> problem, happing in some recent kernel. I'm running 2.6.35-tuxonice-r1
> now, and I no longer have them. But that might also have come from an
> update of lvm2.
>
> 	Wonko
>

Thanks. Here is what I have at the moment


 >  emerge --info
Portage 2.1.8.3 (default/linux/amd64/10.0/no-multilib, gcc-4.4.3, 
glibc-2.11.2-r0, 2.6.34-gentoo-r6 x86_64)
=================================================================
System uname: 
Linux-2.6.34-gentoo-r6-x86_64-Intel-R-_Core-TM-_i7_CPU_L_640_@_2.13GHz-with-gentoo-1.12.13
Timestamp of tree: Sun, 12 Sep 2010 15:45:01 +0000

Maybe the messages will go away next time I sync and update gentoo.

--
Valmor