Re: [vserver] Memory limit problem (solved)

From: Petar Hitij <petahi_at_gmail.com>
Date: Fri 23 May 2008 - 21:47:48 BST
Message-ID: <c6b5fdd40805231347m682f54edw18bc120b8631e903@mail.gmail.com>

Hello Sam,

The 16MB fstab entry is allocated in RAM, increasing it to 300MB is
not a very good idea.

It would be better to comment out the /tmp line in
/etc/vservers/vserver_name/fstab.

Regards
Petar

On Fri, May 23, 2008 at 5:19 AM, Sam Przyswa <samp@arial-concept.com> wrote:
>
> Le vendredi 23 mai 2008 à 03:37 +0200, Sam Przyswa a écrit :
>> Hi Vserver Users,
>>
>> I have a strange problem, I installed the same filesystem's machine
>> (clone) on 2 vservers' machines (same vserver kernel) one on the same
>> file system /var/lib/vserver/ and one other on a LVM logical volume
>> mounted on /var/lib/vserver/ and create the two vservers with the same
>> command.
>>
>> The two vservers work fine but on my machine with LVM it seems to be a
>> memory problem when I try to extract a big tar.gz file (80Mb) I have 3Gb
>> memory on this machine and the filesystem (LVM) is 33% free, I got an
>> error message "gzip: stdout: No space left on device" I don't have this
>> problem on the other machine with 1Gb memory !?
>
> In fact the tar.gz was in /tmp directory and this directory was mounted
> with only 16Mb in the fstab, I rise the size to 300Mb in fstab and then
> everything work fine now.
>
> Perhaps this help somebody...
>
> Sam.
>
>
>
>
>
Received on Fri May 23 21:48:08 2008

[Next/Previous Months] [Main vserver Project Homepage] [Howto Subscribe/Unsubscribe] [Paul Sladen's vserver stuff]
Generated on Fri 23 May 2008 - 21:48:12 BST by hypermail 2.1.8