From: Roman Mamedov <rm@romanrm.net>
To: Liu Bo <bo.li.liu@oracle.com>
Cc: "Михаил Гаврилов" <mikhail.v.gavrilov@gmail.com>,
"Chris Murphy" <lists@colorremedies.com>,
"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: Re: task btrfs-cleaner:770 blocked for more than 120 seconds.
Date: Mon, 15 Feb 2016 03:42:19 +0500 [thread overview]
Message-ID: <20160215034219.2f0df0ce@natsu> (raw)
In-Reply-To: <20160214213224.GB28882@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1663 bytes --]
On Sun, 14 Feb 2016 13:32:24 -0800
Liu Bo <bo.li.liu@oracle.com> wrote:
> Hi Mike,
> On Sun, Feb 14, 2016 at 12:23:16AM +0500, Михаил Гаврилов wrote:
> > Sorry, I have not yet had time to apply your patch.
> >
> > And get hang again when launch web browser.
> >
> > Here new logs: http://btrfs.sy24.ru/kernel-sysrqw-btrfscleaner770blocked-3.txt
>
> The logs show,
> every hung process is waiting for fs tree root's WRITE_LOCK, but someone who's
> holding the WRITE_LOCK is not reflected here.
>
> Only one suspicious process is
> "Chrome_FileThre D ffff8807fe1d7a18 10360 22486 2826 0x00000000"
> it's also waiting on btrfs_tree_lock(), but I can't tell whether it
> waits for the fs tree root node's lock or the children node's lock.
>
> Hmm, sorry for not being helpful, but I was wondering if this also
> occurs on the latest btrfs(4.5) or is it possible to give it a shot?
>
> The best result is that it's been fixed by one commit in 4.5.
FWIW I had a persistently repeating deadlock on 4.1 and 4.3, but after upgrade
to 4.4 it no longer happens. Not sure if it might be related or not, the
backtrace seems similar: http://www.spinics.net/lists/linux-btrfs/msg50951.html
My advice would be to try 4.4, but don't forget to manually add the
nocow/enospc patch: https://patchwork.kernel.org/patch/7967161/
None of the vanilla 4.1, 4.3 or 4.4 should be considered usable with Btrfs at
the moment. The latest kernel series which works out of the box was 3.18;
patched 4.4 also works fine so far, but I wonder if that patch makes it into
4.4.2 or gets forgotten/etc again.
--
With respect,
Roman
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-02-14 22:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 20:20 task btrfs-cleaner:770 blocked for more than 120 seconds Михаил Гаврилов
2016-02-03 0:41 ` Liu Bo
2016-02-03 2:45 ` Chris Murphy
[not found] ` <CABXGCsOAyYa96E965ruKp9evCY3FrCdBr-GTPvCws5VqmjUC5Q@mail.gmail.com>
2016-02-03 4:37 ` Chris Murphy
2016-02-03 4:48 ` Chris Murphy
2016-02-10 20:39 ` Михаил Гаврилов
2016-02-10 21:23 ` Chris Murphy
2016-02-11 19:18 ` Liu Bo
2016-02-11 21:03 ` Михаил Гаврилов
2016-02-12 3:22 ` Liu Bo
2016-02-12 3:38 ` Chris Murphy
2016-02-12 20:35 ` Liu Bo
2016-02-12 19:15 ` Михаил Гаврилов
2016-02-12 20:34 ` Liu Bo
2016-02-13 19:23 ` Михаил Гаврилов
2016-02-14 21:32 ` Liu Bo
2016-02-14 22:42 ` Roman Mamedov [this message]
2016-02-18 12:35 ` Christian Rohmann
2016-02-18 16:59 ` Liu Bo
2016-02-19 16:00 ` Christian Rohmann
2016-02-19 16:42 ` Chris Murphy
[not found] ` <CABXGCsOVeEBn9A=Wj6VtAEsban6LKj6B958gN8JqK9omLjDt9A@mail.gmail.com>
2016-03-16 9:01 ` Roman Mamedov
2016-03-16 19:54 ` Михаил Гаврилов
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=20160215034219.2f0df0ce@natsu \
--to=rm@romanrm.net \
--cc=bo.li.liu@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=mikhail.v.gavrilov@gmail.com \
/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).