From: Chris Mason <clm@fb.com>
To: Marc MERLIN <marc@merlins.org>
Cc: Roman Mamedov <rm@romanrm.net>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: 3.16.3: fs/btrfs/delayed-inode.c:1410 btrfs_assert_delayed_root_empty
Date: Mon, 29 Dec 2014 10:57:14 -0500 [thread overview]
Message-ID: <1419868634.13012.19@mail.thefacebook.com> (raw)
In-Reply-To: <20141229154144.GC17254@merlins.org>
On Mon, Dec 29, 2014 at 10:41 AM, Marc MERLIN <marc@merlins.org> wrote:
> On Mon, Dec 29, 2014 at 10:17:00AM -0500, Chris Mason wrote:
>> I've hit this recently on my laptop, and haven't yet been able to
>> recreate it on a machine where I can debug things. The messages are
>> an error in the log tree replay code, and I don't think they are
>> actually related to any corruptions. Trying to nail it down today.
>
> Thanks for the update and looking at it.
>
> Just to rule things out for me, on your laptop, are you running btrfs
> directly on disk, or do you have layers like dmcrypt in the middle?
> (having 2 other layers myself, I never know if it's btrfs that could
> be
> to blame, or the other 2 layers not passing data through in atomic
> bits
> like they're supposed to)
I do have dmcrypt, but I really think this is only in btrfs.
-chris
next prev parent reply other threads:[~2014-12-29 15:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-28 19:26 3.16.3: fs/btrfs/delayed-inode.c:1410 btrfs_assert_delayed_root_empty Marc MERLIN
2014-12-28 20:00 ` Roman Mamedov
2014-12-28 21:36 ` Marc MERLIN
2014-12-29 15:17 ` Chris Mason
2014-12-29 15:41 ` Marc MERLIN
2014-12-29 15:57 ` Chris Mason [this message]
2014-12-30 1:06 ` Qu Wenruo
2014-12-31 18:30 ` [PATCH] Btrfs: don't delay inode ref updates during log replay Chris Mason
2015-01-01 22:58 ` Marc MERLIN
2015-01-02 0:44 ` Qu Wenruo
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=1419868634.13012.19@mail.thefacebook.com \
--to=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.org \
--cc=rm@romanrm.net \
/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).