OpenVZ Forum


Home » Mailing lists » Users » cat: /proc/self/mountinfo: Cannot allocate memory
Re: Re: cat: /proc/self/mountinfo: Cannot allocate memory [message #45490 is a reply to message #45216] Tue, 13 March 2012 07:32 Go to previous messageGo to previous message
Andrew Vagin is currently offline  Andrew Vagin
Messages: 28
Registered: November 2011
Junior Member
Hello Benjamin,

Pls, file this bug in https://bugzilla.openvz.org/

On 02/14/2012 03:07 PM, Benjamin Henrion wrote:
> On Tue, Feb 14, 2012 at 11:48 AM, Benjamin Henrion<bh@udev.org> wrote:
>> On Tue, Feb 14, 2012 at 11:29 AM, Benjamin Henrion<bh@udev.org> wrote:
>>> On Tue, Feb 14, 2012 at 11:26 AM, Benjamin Henrion<bh@udev.org> wrote:
>>>> Hi,
>>>>
>>>> I am trying updatedb on a gentoo openvz container, the HN is a debian
>>>> squeeze kernel.
>>>>
>>>> Updatedb segfaults, and when I strace it, I find that:
>>>>
>>>> # cat /proc/self/mountinfo
>>>> cat: /proc/self/mountinfo: Cannot allocate memory
>>>>
>>>> Any idea how to fix that?
>>>>
>>>> There is a bug filed here:
>>>>
>>>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655385
>>>>
>>>> But I have no idea how to fix it.
>>> I see there was a kernel crash here, that might explain something:
>> In fact, the updatedb **triggered** the kernel module crash. Not the
>> other way around.
> I tried with the latest update from debian:
>
> Linux version 2.6.32-5-openvz-amd64 (Debian 2.6.32-41) (ben@decadent.org.uk)
>
> Same kernel crash.
>
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: music and movie in the CT during the migration
Next Topic: occasional high loadavg without any noticeable cpu/memory/io load
Goto Forum:
  


Current Time: Wed May 22 01:30:25 GMT 2024

Total time taken to generate the page: 0.01603 seconds