linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: chuck gelm <chuck@gelm.net>
To: fluca1978@infinito.it
Cc: linux-admin@vger.kernel.org
Subject: Re: zip error: out of memory
Date: Thu, 29 Jul 2004 17:57:56 -0400	[thread overview]
Message-ID: <410972E4.3050008@gelm.net> (raw)
In-Reply-To: <200407291511.15582.fluca1978@infinito.it>

Luca Ferrari wrote:
> On Wednesday 28 July 2004 22:17 chuck gelm's cat walking on the keyboard  
> wrote:
> 
> 
>>Luca Ferrari wrote:
>>
>>>Hi,
>>>I was doing a backup of a NFS partition (about 300 MB) using zip but I
>>>got the error:
>>>Zip error: Out of memory (allocating temp filename)
>>>I've tried to find some information but I was unable. Since I've used zip
>>>to compress SMB partitions over 1 GB I don't believe that it can be a
>>>"size" problem. I've tried to specify the temporary directory with the -b
>>>flag, but nothing changed. On my disk I've got about 11 GB of free space,
>>>so have you any idea or suggestion about this problem?
>>>
>>>Thanks,
>>>Luca
>>
>>Hi, Luca:
>>
>>  Show us exactly what you did (the exact command line).
>>Show us the free space of your 'cwd' and your temporary directory.
>>Show us the size of the partition you are trying to backup.
>>
>>Perhaps you could run 'watch -d df' on another console and see
>>what directory is getting 'Out of memory' or
>>  your could run 'free -s 9' on another console to see if you
>>  are running out of RAM memory.
>>
> 
> 
> Here's the command line I use:
> 
> /usr/bin/zip  -r -u -y -b /tmp/backup  /mnt/disco2//letizia.zip * 
> 
> zip error: Out of memory (allocating temp filename)
> 
> and the memory as reported by free before and during the zipping:
> 
>              total       used       free     shared    buffers     cached
> Mem:        256624     253180       3444          0      40412      85796
> -/+ buffers/cache:     126972     129652
> Swap:      1020088         16    1020072
> 
>              total       used       free     shared    buffers     cached
> Mem:        256624     254096       2528          0      34604      92080
> -/+ buffers/cache:     127412     129212
> Swap:      1020088         16    1020072
> 
> 
> Any idea?
> 
> Luca

Yes.
Is '/tmp/backup' a directory or a regular file?

If the directory '/tmp' already exists,
  try that command line, but swap '/tmp/backup' with '/tmp'.
I am guessing that the directory 'backup' does not already
exist under '/tmp' or you cannot create the directory
'/tmp/backup' because it already exists as a regular file
or you cannot write to the directory.

What is the free space of '/tmp'?
Show us the output of 'df'.
Do you have 'rights' to create files under '/tmp'?
  (are you running 'zip' as 'root' ?)
Make sure that you have correct access rights to '/tmp/backup'.

HTH, Chuck


  parent reply	other threads:[~2004-07-29 21:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-28 15:35 zip error: out of memory Luca Ferrari
2004-07-28 19:40 ` Chris DiTrani
2004-07-29 17:06   ` Glynn Clements
2004-07-28 20:17 ` chuck gelm
2004-07-29 13:11   ` Luca Ferrari
2004-07-29 14:20     ` Chris DiTrani
2004-07-29 21:57     ` chuck gelm [this message]
2004-07-30  8:50       ` Luca Ferrari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=410972E4.3050008@gelm.net \
    --to=chuck@gelm.net \
    --cc=fluca1978@infinito.it \
    --cc=linux-admin@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).