On Mon, Mar 28, 2016 at 04:14:46PM +0200, Markus Trippelsdorf wrote: > On 2016.03.28 at 10:05 -0400, Josef Bacik wrote: > > >Mar 24 10:37:27 x4 kernel: WARNING: CPU: 3 PID: 11838 at fs/btrfs/inode.c:9261 btrfs_destroy_inode+0x22b/0x2a0 > > > > I saw this running some xfstests on our internal kernels but haven't been > > able to reproduce it on my latest enospc work (which is obviously perfect). > > What were you doing when you tripped this? I'd like to see if I actually > > did fix it or if I still need to run it down. Thanks, > > I cannot really tell. Looking at the backtrace, both Dave and I were > running rm. > This warning happened just once on my machine, so the issue is obviously > very hard to trigger. On the other hand, it seems to be triggering really often (on the order of ~10 mins of light use) on my box. I understandably ran away from 4.6-rc to stable kernels (no one likes to risk data loss), but even in that little time it triggered 328 times (over ~20ish boots). Despite all of these WARNs, there's no data loss yet on the disk in question, and the filesystem appears consistent. Call stacks show a variety of callers of btrfs_destroy_inode, originating from do_unlinkat, SyS_rename, btrfs_ioctl_snap_destroy, shrink_zone, or task_work_run, direct callers being: do_unlinkat __dentry_kill dput __dentry_kill shrink_dentry_list dispose_list prune_icache_sb Just tried 4.6-rc5, it's still there. Any way I could help debug this? -- A tit a day keeps the vet away. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
