From: Gordan Bobic <gordan-UpbECiGlrmGsTnJN9+BGXg@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Questions on nilfs_cleanerd
Date: Wed, 07 Mar 2012 09:31:05 +0000 [thread overview]
Message-ID: <4F572AD9.3080705@bobich.net> (raw)
In-Reply-To: <CAHmELnXB7LFwDRR53G_kCWb9t5wfWQOXDq=0xRC5bh9Z3TJuuw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
These sound similar to the questions/concerns I raised a while back.
> 1) Does the daemon read/write the entire drive to look for dead blocks to clean?
Yes - sequentially (and then it rolls over to the beginning again).
> 2) What if there aren't any dead blocks to clean and the free space in
> the drive is still less than 10% (the default min_clean_segments in
> the conf file), does the daemon still process the drive? If so, how do
> I change the cleaning interval so that it doesn't process the drive as
> often?
The only worthwhile suggestion I heard is to set the minimum history
retention rate (the FS is continuously snapshotting) to 1 day. That way
you can guarantee the churn rate will never exceed the capacity of the
disk per day. Not ideal, but at least it puts some kind of a hard limit
on how quickly it'll waste your flash - at the expense of making the
problem of the non-determinism of free space a little worse.
Gordan
--
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
prev parent reply other threads:[~2012-03-07 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 6:13 Questions on nilfs_cleanerd Kenneth Langga
[not found] ` <CAHmELnXB7LFwDRR53G_kCWb9t5wfWQOXDq=0xRC5bh9Z3TJuuw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-07 9:31 ` Gordan Bobic [this message]
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=4F572AD9.3080705@bobich.net \
--to=gordan-upbeciglrmgstnjn9+bgxg@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.