From: "Carlos R. Mafra" <crmafra2@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs write behavior on idle system
Date: Mon, 18 Jan 2010 18:35:25 +0100 [thread overview]
Message-ID: <20100118173525.GA4629@Pilar.aei.mpg.de> (raw)
In-Reply-To: <20100118171756.GA4165@Pilar.aei.mpg.de>
PS:
On Mo 18.Jan'10 at 18:17:56 +0100, Carlos R. Mafra wrote:
> ...
> [ I get really worried when I 'blktrace -a write' my /home when actively
> using chrome. Just a 2-minute experiment here while I was writing this
> email ended up like this:
>
...
> blktrace (4226)
> Reads Queued: 0, 0KiB Writes Queued: 0, 0KiB
> Read Dispatches: 0, 0KiB Write Dispatches: 0, 0KiB
> Reads Requeued: 0 Writes Requeued: 0
> Reads Completed: 0, 0KiB Writes Completed: 8, 204KiB
This time I was inside /home taking the blktrace, but I usually do it from
inside /root which is in /dev/sda2 and uses ext4 to avoid disturbing
the result of measuring what is going on with btrfs in /dev/sda3.
next prev parent reply other threads:[~2010-01-18 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 17:17 btrfs write behavior on idle system Carlos R. Mafra
2010-01-18 17:35 ` Carlos R. Mafra [this message]
2010-01-18 18:14 ` Ravi Pinjala
2010-01-18 19:36 ` Carlos R. Mafra
2010-01-20 21:29 ` Chris Mason
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=20100118173525.GA4629@Pilar.aei.mpg.de \
--to=crmafra2@gmail.com \
--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