Original Message
Subject: Re: 3.16.3: fs/btrfs/delayed-inode.c:1410
btrfs_assert_delayed_root_empty
From: Roman Mamedov
To: Marc MERLIN
Date: 2014年12月29日 04:00
On Sun, 28 Dec 2014 11:26:14 -0800
Marc MERLIN wrote:
Not sure if it's useful to anyone, but there y
On Mon, Dec 29, 2014 at 10:41 AM, Marc MERLIN 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
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 corrup
On Sun, Dec 28, 2014 at 4:36 PM, Marc MERLIN wrote:
On Mon, Dec 29, 2014 at 01:00:47AM +0500, Roman Mamedov wrote:
> Will btrfs scrub, even if it takes about 24H to run for me, tell
me
> which FS is affected and if so do I run btrfs repair?
I had this:
https://urldefense.proofpoint.com/v1
On Mon, Dec 29, 2014 at 01:00:47AM +0500, Roman Mamedov wrote:
> > Will btrfs scrub, even if it takes about 24H to run for me, tell me
> > which FS is affected and if so do I run btrfs repair?
>
> I had this: http://www.spinics.net/lists/linux-btrfs/msg40586.html
>
> 1) I determined which btrfs o
On Sun, 28 Dec 2014 11:26:14 -0800
Marc MERLIN wrote:
> Not sure if it's useful to anyone, but there you go. This happened after a
> forced
> power cycle:
>
> BTRFS info (device dm-1): disk space caching is enabled
> [ cut here ]
> WARNING: CPU: 2 PID: 778 at fs/btrfs/de
