Linux NILFS development
 help / color / mirror / Atom feed
From: Alexander Schier <alex-W0ZHf6uU1cg@public.gmane.org>
To: NILFS Users mailing list <users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
Subject: Re: OOM while deleting very large files
Date: Mon, 5 May 2008 18:53:31 +0200	[thread overview]
Message-ID: <20080505165331.GA15115@laxu.de> (raw)
In-Reply-To: <20080506.011837.81573783.ryusuke-sG5X7nlA6pw@public.gmane.org>

Hi!
On Tue, May 06, 2008 at 01:18:37AM +0900, Ryusuke Konishi wrote:
It is not so important, as i do not need to use such big files further,
so you can have holydays ;).

For the fixing later:
PC: 
CPU: AMD Athlon XP 1,6+
RAM: 512 MB DDR RAM
Nilfs2 Version (Module and Tools): 2.0.2
Partition: 251 GB dmcrypt
Files: 2x approx. 100 GB created with dd if=/dev/zero of=bigfile, to
erase the old content on the cryptopartition (the zeros are written
encrypted to the real partition)

Problem while deleting them as described:
> > rm bigfile1
> > 
> > or after it failed
> > 
> > echo '' >bigfile1
> > 
> > the pc worked a long time, and then nilfs2 used so much ram, that the
> > kernel killed all programs, and finally the pc was unusable. It was not
> > possible to delete the files, other than reformatting the partition.

Now i'm using the same setup with a nilfs2 with "normal" files on it,
filled to 11 GB (df -h), without any further problems. 

I do not want to
experiment in a way, that the partition needs to be reformatted later
again :/.

Alex

  parent reply	other threads:[~2008-05-05 16:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-04 16:54 OOM while deleting very large files Alexander Schier
     [not found] ` <20080504165426.GA2826-W0ZHf6uU1cg@public.gmane.org>
2008-05-05 16:18   ` Ryusuke Konishi
     [not found]     ` <20080506.011837.81573783.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-05-05 16:53       ` Alexander Schier [this message]
     [not found]         ` <20080505165331.GA15115-W0ZHf6uU1cg@public.gmane.org>
2008-05-05 17:39           ` Ryusuke Konishi

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=20080505165331.GA15115@laxu.de \
    --to=alex-w0zhf6uu1cg@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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