From: dexen deVries <dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs <linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: Paolo Giangrandi <paolo-UnihLHphgvQ1GQ1Ptb7lUw@public.gmane.org>
Subject: Re: nilfs2 not garbage collecting
Date: Thu, 09 Aug 2012 13:17:30 +0200 [thread overview]
Message-ID: <2382169.a90FXUemaH@coil> (raw)
In-Reply-To: <CANku=gha48jamDmmK6CxVEypryXPniPcgJ3BYa7zYm1EDyYGEg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Thursday 09 of August 2012 12:33:09 you wrote:
> I'm having some issues at uploading the compressed image (it's "just"
> 2.3GB, but with my current connection it would take days, I'll upload
> it on september).
>
> Meanwhile nilfs_cleanerd managed to free some more space (over 1GB),
> although nothing has changed since yesterday, thus everything seems
> back to normality.
> Thanks for the help and see you in september!
when i'm in a pinch and want cleanerd to free up some space, i run:
# while true; do killall -HUP nilfs_cleanerd; sleep 4; done
each `HUP' signal causes cleanerd to both re-read config and run single pass.
i then monitor progress with
# iostat -dk 1 /dev/sda
to see if it is moving data around. if not, i lower `protection_period' in
/etc/nilfs_cleanerd.conf; I usually have it set to 7 to 14 days on personal
computers, but when /really/ in a squeeze for free space, i lower it to 24h.
you may also want to increase `nsegments_per_clean' in nilfs_cleanerd.conf to
3 (but not much more; each segment causes up to 8MB of read and write upon
each cleanerd pass).
cheers,
--
dexen deVries
[[[↓][→]]]
--
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:[~2012-08-09 11:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANku=ggohcWWoxE1x=XmfWpANKyWRTWb5p_aHh8LU6+utU4OPQ@mail.gmail.com>
[not found] ` <CANku=ggohcWWoxE1x=XmfWpANKyWRTWb5p_aHh8LU6+utU4OPQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-05 11:00 ` nilfs2 not garbage collecting Paolo Giangrandi
[not found] ` <CANku=ghnDzkFHpPZ8eT9Y3kTM62zBKMk6TjBVraE4Kisa1TRPQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-05 13:31 ` Vyacheslav Dubeyko
2012-08-05 13:44 ` Vyacheslav Dubeyko
[not found] ` <CANku=gjkTr-nYq8RxTUCVK9YU+xTjHyPbktB86BUpeuMwMBC4A@mail.gmail.com>
[not found] ` <CANku=gjkTr-nYq8RxTUCVK9YU+xTjHyPbktB86BUpeuMwMBC4A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-05 16:51 ` Vyacheslav Dubeyko
[not found] ` <D99F26AB-309D-4325-A87C-DBF0F7BA6360-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2012-08-06 11:48 ` Piotr Szymaniak
2012-08-06 13:48 ` Paolo Giangrandi
2012-08-05 13:54 ` Vyacheslav Dubeyko
[not found] ` <CANku=ghdeeSLP6QsJh9jvs5fJwEYuTTV7w8iigE1nZoT74NYgQ@mail.gmail.com>
2012-08-05 16:52 ` Fwd: " Vyacheslav Dubeyko
[not found] ` <CANku=ghdeeSLP6QsJh9jvs5fJwEYuTTV7w8iigE1nZoT74NYgQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-06 5:54 ` Vyacheslav Dubeyko
2012-08-06 14:07 ` Paolo Giangrandi
[not found] ` <CANku=ggMp_gBgijee2umhNf5dBQO4zvmqopKBz70V1Z81oShVA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-08 6:13 ` Vyacheslav Dubeyko
2012-08-08 15:08 ` Paolo Giangrandi
[not found] ` <CANku=gjA=_Up4OJPLGU4P+8Zw3o8=J3BGFWTgPsHd9d=uUV_PA@mail.gmail.com>
[not found] ` <CANku=gjA=_Up4OJPLGU4P+8Zw3o8=J3BGFWTgPsHd9d=uUV_PA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-08 17:54 ` Vyacheslav Dubeyko
[not found] ` <3170A27E-46DD-4347-8F9B-FBF4BB4E0205-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2012-08-09 10:33 ` Paolo Giangrandi
[not found] ` <CANku=gha48jamDmmK6CxVEypryXPniPcgJ3BYa7zYm1EDyYGEg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-09 11:17 ` dexen deVries [this message]
2012-08-09 12:46 ` Christian Smith
2012-08-08 18:01 ` Vyacheslav Dubeyko
2012-08-06 10:10 ` Piotr Szymaniak
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=2382169.a90FXUemaH@coil \
--to=dexen.devries-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=paolo-UnihLHphgvQ1GQ1Ptb7lUw@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;
as well as URLs for NNTP newsgroup(s).