From: Chris Mason <clm@fb.com>
To: john terragon <jterragon@gmail.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: kernel 3.17-rc3: task rsync:2524 blocked for more than 120 seconds
Date: Mon, 1 Sep 2014 12:02:55 -0400 [thread overview]
Message-ID: <540498AF.6030109@fb.com> (raw)
In-Reply-To: <CANg_oxzqyr3Jcx-8ntPPntjVmRjWqheUqaWOWpkhh5Rrw3Ayrw@mail.gmail.com>
On 09/01/2014 09:33 AM, john terragon wrote:
> Hi.
>
> I'm not sure if this is related to the hung task problem that I've
> been seeing in this ml for a while. But I've been having this
> seemingly related problem with 3.15, 3.16 and now 3.17-rc3 (which, if
> I'm not mistaken, should have a fix for the hung task problem). So
> here it is: I have a usb flash drive with btrfs (on top of dmcrypt)
> usually mounted with these options
>
> rw,noatime,compress-force=zlib,ssd,space_cache,autodefrag
>
> When I try to rsync the usb flash drive I get a truck-load of "INFO:
> task rsync:2524 blocked for more than 120 seconds" as you can see
> below.
> The rsync process crawls into an almost complete stop and I can't even
> kill it. I know the usb key is OK because I've tried the same thing
> with ext4 and xfs and everything went fine.
This does have all of our fixes for hangs. Does the rsync eventually
complete? Or do we just sit there forever?
-chris
next prev parent reply other threads:[~2014-09-01 16:03 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 [this message]
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
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=540498AF.6030109@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.