From: Stephane Chazelas <stephane_chazelas@yahoo.fr>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: curious writes on mounted, not used btrfs filesystem
Date: Sun, 22 May 2011 10:34:03 +0100 [thread overview]
Message-ID: <20110522093352.GA22491@yahoo.fr> (raw)
In-Reply-To: <4DD7B6ED.5040403@wpkg.org>
2011-05-21 14:58:21 +0200, Tomasz Chmielewski:
> I have a btrfs filesystem (2.6.39) which is mounted, but otherwise, not used:
>
> # lsof -n|grep /mnt/btrfs
processes with open fds are one thing. You could also have loop
devices setup on it for instance.
> #
>
>
> I noticed that whenever I do "sync", btrfs will write for around 6.5s and write 13 MB (see below).
[...]
You could try and play with /proc/sys/vm/block_dump to see what
is being written (remember to disable logging of kernel messages
by syslog).
--
Stephane
next prev parent reply other threads:[~2011-05-22 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-21 12:58 curious writes on mounted, not used btrfs filesystem Tomasz Chmielewski
2011-05-22 9:34 ` Stephane Chazelas [this message]
2011-05-22 9:52 ` Tomasz Chmielewski
2011-05-22 18:26 ` Stephane Chazelas
2011-05-22 15:21 ` Swâmi Petaramesh
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=20110522093352.GA22491@yahoo.fr \
--to=stephane_chazelas@yahoo.fr \
--cc=linux-btrfs@vger.kernel.org \
--cc=mangoo@wpkg.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).