Linux NILFS development
 help / color / mirror / Atom feed
From: "Łukasz Wójcicki" <lwojcicki-V+nj596LuoKHKKo6LODCOg@public.gmane.org>
To: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
Cc: jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org,
	linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Limits for checkpoints
Date: Fri, 09 Jul 2010 18:16:21 +0200	[thread overview]
Message-ID: <1278692181.7532.1.camel@Stanowisko-25> (raw)
In-Reply-To: <20100709.200552.176154048.ryusuke-sG5X7nlA6pw@public.gmane.org>


> If you worry about the disk usage of df output, one of the way is
> adjusting min_clean_segments and max_clean_segments in
> /etc/nilfs_cleanerd.conf.
> 
> In the latest version of nilfs, nilfs_cleanerd tries to store past
> data until free space gets less than 10% of the disk capacity.
> 
> By decreasing those parameters, or by setting min_clean_segments to
> zero this behavior is adjustable.

Are these parameters will work with the version of kernel module
2-0-18 ?

Regards,
Łukasz Wójcicki

--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2010-07-09 16:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-08 12:56 How to turn off checkpoints Łukasz Wójcicki
     [not found] ` <AANLkTimD74YP7GC1imbiRnKGETOfLYlGMkO682GqeU90@mail.gmail.com>
     [not found]   ` <AANLkTimD74YP7GC1imbiRnKGETOfLYlGMkO682GqeU90-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-09  1:11     ` Ryusuke Konishi
     [not found]       ` <AANLkTimfmo7MOXJpEgE-0psC6jnCt0S0BRopxoxWrc_l-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-09  5:13         ` Limits for checkpoints Łukasz Wójcicki
2010-07-09  5:30           ` Jiro SEKIBA
     [not found]             ` <87eifd9q88.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2010-07-09  5:38               ` Łukasz Wójcicki
2010-07-09 11:05                 ` Ryusuke Konishi
     [not found]                   ` <20100709.200552.176154048.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-07-09 16:16                     ` Łukasz Wójcicki [this message]
     [not found]                       ` <AANLkTikPhJGn45cLRcndvki4GSfpAzrdo8V7fbkmfo3o@mail.gmail.com>
     [not found]                         ` <AANLkTikPhJGn45cLRcndvki4GSfpAzrdo8V7fbkmfo3o-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-10  7:14                           ` 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=1278692181.7532.1.camel@Stanowisko-25 \
    --to=lwojcicki-v+nj596luokhkko6lodcog@public.gmane.org \
    --cc=jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ryusuke-sG5X7nlA6pw@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