From: Tomasz Chmielewski <mangoo@wpkg.org>
To: linux-btrfs <linux-btrfs@vger.kernel.org>, jonas@lophus.org
Subject: Re: Writes in idle/How to debug filesystem activity
Date: Tue, 30 Aug 2011 08:58:40 +0200 [thread overview]
Message-ID: <4E5C8A20.7030604@wpkg.org> (raw)
> I use btrfs on a SD card. When my computer is running in idle (i.e.
> nothing running but wmii and a few background tasks that don't do any
> i/o; freshly synced), from time to time some [btrfs-*] tasks do writes
> (for 5 seconds or so). What are those processes doing on my disk,
> having nothing to write/read? That leads to the second question: How can
> I debug file system activity in inotify style?
There was once a similar thread about this issue; unfortunately, without
any constructive answers:
http://thread.gmane.org/gmane.comp.file-systems.btrfs/10840
--
Tomasz Chmielewski
http://wpkg.org
next reply other threads:[~2011-08-30 6:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 6:58 Tomasz Chmielewski [this message]
2011-08-30 7:06 ` Writes in idle/How to debug filesystem activity cwillu
-- strict thread matches above, loose matches on Subject: below --
2011-08-29 20:13 Jonas H.
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=4E5C8A20.7030604@wpkg.org \
--to=mangoo@wpkg.org \
--cc=jonas@lophus.org \
--cc=linux-btrfs@vger.kernel.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