From: Gordan Bobic <gordan-UpbECiGlrmGsTnJN9+BGXg@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: nilfs_cleanerd using a lot of disk-write bandwidth
Date: Tue, 09 Aug 2011 11:18:12 +0100 [thread overview]
Message-ID: <94b06fe504b540199f338f9bd4ed890f@mail.shatteredsilicon.net> (raw)
Hi,
I'm seeing nilfs_cleanerd using a lot of disk write bandwidth according
to iotop. It seems to be performing approximately equal amounts of reads
and writes when it is running. Reads I can understand, but why is it
writing so much in order to garbage collect? Should it not be just
trying to mark blocks as free? The disk I/O r/w symmetry implies that it
is trying to do something like defragment the file system. Is there a
way to configure this behaviour in some way? The main use-case I have
for nilfs is cheap flash media that suffers from terrible random-write
performance, but on such media this many writes are going to cause media
failure very quickly. What can be done about this?
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
next reply other threads:[~2011-08-09 10:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 10:18 Gordan Bobic [this message]
[not found] ` <94b06fe504b540199f338f9bd4ed890f-tp2ajI7sM87MEvS+BUbURm2TqnkC6wfpXqFh9Ls21Oc@public.gmane.org>
2011-08-09 11:03 ` nilfs_cleanerd using a lot of disk-write bandwidth dexen deVries
[not found] ` <201108091303.54968.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-08-09 12:25 ` Gordan Bobic
[not found] ` <4ef54cf8b3d0b2725aa1788d98ffbbe5-tp2ajI7sM87MEvS+BUbURm2TqnkC6wfpXqFh9Ls21Oc@public.gmane.org>
2011-08-09 15:19 ` dexen deVries
[not found] ` <201108091719.01585.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-08-09 15:45 ` Gordan Bobic
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=94b06fe504b540199f338f9bd4ed890f@mail.shatteredsilicon.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 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).