Linux NILFS development
 help / color / mirror / Atom feed
From: Reinoud Zandijk <reinoud-S783fYmB3Ccdnm+yROfE0A@public.gmane.org>
To: NILFS Users mailing list <users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
Subject: Re: Stressing GC
Date: Thu, 11 Jun 2009 17:20:40 +0200	[thread overview]
Message-ID: <20090611152040.GF21314@aardappel.13thmonkey.org> (raw)
In-Reply-To: <20090611153950.GA26921-F34IG+UkkWQ4ZZIPogyGsg@public.gmane.org>

Dear folks,

On Thu, Jun 11, 2009 at 11:39:50AM -0400, Luis Useche wrote:
> On Thu, Jun 11, 2009 at 08:17:51AM +0400, Dave wrote:
> > On 06/11/09 01:08, Luis Useche wrote:
> > > I was doing some experiments on nilfs2 to stress the garbage collection
> > > with different file system usage. Unfortunately, it was unable to pass the
> > > first test since nilfs reports no space available eventhough there are no
> > > files in the file system! I guess the GC is not collecting space fast
> > > enough and the file system ends up with no space available.
> > > 
> > > Do you have any workaround to this problem?
>
> With the current GC implementation, I am unable to do my experiment. I set
> "protection_period 0" but still have the problem. Besides, this is
> probably not the right solution either since the GC can do unnecessary work
> that can underestimate the potential of nilfs. I need the first option (1)
> from the first paragraph above.
> 
> Are there any workaround I can use to make this work.

idealiter there should be an analog to VMS's purge command, say purge_nilfs or
`nilfs purge /mnt' that flushes all data not protected by a snapshot or the
last checkpoint.

Could this be something?

Another more blunt method is say newfs'ing a disc, create a snapshot sometime,
mess around with it and later revert back to the snapshot.

With regards,
Reinoud

  parent reply	other threads:[~2009-06-11 15:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10 21:08 Stressing GC Luis Useche
     [not found] ` <20090610210859.GA17619-F34IG+UkkWQ4ZZIPogyGsg@public.gmane.org>
2009-06-11  4:17   ` Dave
     [not found]     ` <4A30856F.3000103-/hCUnnzDXf0AvxtiuMwx3w@public.gmane.org>
2009-06-11 15:39       ` Luis Useche
     [not found]         ` <20090611153950.GA26921-F34IG+UkkWQ4ZZIPogyGsg@public.gmane.org>
2009-06-11 15:20           ` Reinoud Zandijk [this message]
     [not found]             ` <20090611152040.GF21314-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>
2009-06-11 16:51               ` Jérôme Poulin
     [not found]                 ` <debc30fc0906110951j4d32efb1xd3f73c0cd07a06e1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-12 15:02                   ` Luis Useche

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=20090611152040.GF21314@aardappel.13thmonkey.org \
    --to=reinoud-s783fymb3ccdnm+yrofe0a@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