Hi Glyn :) On 09/16/15 16:31, Glyn Normington wrote: > We are seeing a very similar problem fwiw. Unfortunately we can't > reproduce this reliably, but it is cropping up regularly. Here's a > chore we are using to track our work on this: [2]. > > Here's the kernel log: > > [610194.395845] WARNING: CPU: 3 PID: 29166 at > /build/linux-lts-vivid-BZwsXG/linux-lts-vivid-3.19.0/fs/btrfs/super.c:260 > __btrfs_abort_transaction+0x54/0x130 [btrfs]() This is an entirely different problem and may have long been fixed; I count at least 6 patches for tx aborts in my 4.1++ tree alone. We're talking about patches that I can guarantee you are not running. If Pivotal needs some help with stable btrfs backport fixes I might be able to resurrect my old 3.19 patch queue (check my Github!), but this is close to Zombie Olympics.. :) cheers Holger -- 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
