From: Chris Mason <clm@fb.com>
To: john terragon <jterragon@gmail.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: kernel 3.17-rc3: task rsync:2524 blocked for more than 120 seconds
Date: Wed, 3 Sep 2014 08:36:47 -0400 [thread overview]
Message-ID: <54070B5F.20100@fb.com> (raw)
In-Reply-To: <CANg_oxxn-4LXnG5t_wgX=ZvkLHc2tT8+TY-WEsn2awUTBsHSfA@mail.gmail.com>
On 09/02/2014 09:31 PM, john terragon wrote:
> Rsync finished. FWIW in the end it reported an average speed of about
> 900K/sec. Without autodefrag there have been no messages about hung
> kworkers even though rsync seemingly keeps getting hung for several
> minutes throughout the whole execution.
So lets take a step back and figure out how fast the usb stick actually is.
This will erase your usb stick, but give us an idea of its performance:
dd if=/dev/zero of=/dev/<wherever you mkfs btrfs> bs=20M oflag=direct count=100
Note again, the above command will erase your usb stick ;) Use whatever device name
you've been sending to mkfs.btrfs
The kernel will allow a pretty significant amount of ram to be dirtied before
forcing writeback, which is why you're seeing rsync stall at seemingly strange
intervals. In the base of btrfs with compression, we add some worker threads between
rsync and the device, and these may be turning the writeback into a somewhat
more bursty operation.
-chris
next prev parent reply other threads:[~2014-09-03 12:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 13:33 kernel 3.17-rc3: task rsync:2524 blocked for more than 120 seconds john terragon
2014-09-01 16:02 ` Chris Mason
2014-09-01 16:36 ` john terragon
2014-09-02 5:20 ` Duncan
2014-09-02 6:12 ` john terragon
2014-09-02 6:40 ` Duncan
2014-09-02 19:56 ` john terragon
2014-09-02 20:10 ` Chris Mason
2014-09-02 20:23 ` john terragon
2014-09-02 20:48 ` john terragon
2014-09-03 1:31 ` john terragon
2014-09-03 12:36 ` Chris Mason [this message]
2014-09-03 14:11 ` john terragon
2014-09-03 15:02 ` Chris Murphy
2014-09-03 2:44 ` Chris Murphy
2014-09-03 5:37 ` Duncan
2014-09-03 6:03 ` john terragon
2014-09-03 9:14 ` Liu Bo
2014-09-03 3:32 ` Zygo Blaxell
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=54070B5F.20100@fb.com \
--to=clm@fb.com \
--cc=jterragon@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;
as well as URLs for NNTP newsgroup(s).