From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: sandr8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: nilfs_cleanerd could use some sensible defaults if its conf file is empty...
Date: Mon, 04 Apr 2011 19:00:37 +0900 (JST) [thread overview]
Message-ID: <20110404.190037.212385465.ryusuke@osrg.net> (raw)
In-Reply-To: <BANLkTi=r2nmV1B9nF=f23fk2YxDch0ewRQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Sun, 3 Apr 2011 13:49:47 -0700, Alessandro Salvatori wrote:
> Hello,
>
> my root nilfs2 filesystem filled and trying and editing
> /etc/nilfs_cleanerd.conf resulted in an empty file.
>
> I started the cleanerd but it wasn't freeing up any space.
> Then I converted all of my snapshots back onto checkpoints and removed
> all of my checkpoints.
>
> still nothing.
Did you try '-p' option?
nilfs_cleanerd tries to protect recent checkpoints within the period
specified with "protection_period" parameter.
It is set to one hour by default. So, the effect of converting
snapshots back to checkpoints will not appear soon.
But, you can shorten this period by using the '-p' option for
emergency.
> Then I created a new nilfs_cleanerd.conf with sensible values in my
> home directory and pointed nilfs_cleanerd to that.
>
> and finally it worked!!!
>
> maybe nilfs_cleanerd could default to some minimum of -say- the least
> between some small amount of gigabytes and some small percentage of
> the disk size as the minimum space to free if no setting is found in
> the configuration file?
The current nilfs_cleanerd.conf has keyword 'min_clean_segments' to
specify percentage of minimum free space, but the effect of
protection_period is prior to that.
So, adding another parameter sounds worth considering as you pointed
out.
For instance,
emerg_clean_segments 5% # override protection_period
min_clean_segments 10%
max_clean_segments 20%
Am I on the right track?
Thanks,
Ryusuke Konishi
> thank you!
> -alessandro-
> Here i am, A young man,
> A crashing computer program,
> Here is a pen, write out my name.
> --
> 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
--
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
next prev parent reply other threads:[~2011-04-04 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 20:49 nilfs_cleanerd could use some sensible defaults if its conf file is empty Alessandro Salvatori
[not found] ` <BANLkTi=r2nmV1B9nF=f23fk2YxDch0ewRQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-04-04 10:00 ` Ryusuke Konishi [this message]
[not found] ` <20110404.190037.212385465.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-04-04 18:16 ` Alessandro Salvatori
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=20110404.190037.212385465.ryusuke@osrg.net \
--to=ryusuke-sg5x7nla6pw@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sandr8-Re5JQEeQqe8AvxtiuMwx3w@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