On Tue, Apr 25, 2017 at 11:50 AM, Christophe de Dinechin <[email protected]> wrote:
> > The last filesystem corruption is documented here: > https://bugzilla.redhat.com/show_bug.cgi?id=1444821. The dmesg log is in > there. And also from the bug: >How reproducible: Seen at least 4 times on 3 different disks and 2 different >systems. I've been using Fedora and Btrfs on 1/2 dozen different kinds of hardware since around Fedora 13. The oldest file systems are about 2 years old. I've not seen file system corruption. So I'd say there's some kind of workload that's helping to trigger it or it's hardware related; that it's happening on multiple systems makes me wonder if it's power related. > > The btrfsck crash is here: > https://bugzilla.redhat.com/show_bug.cgi?id=1435567. I have two crash modes: > either an abort or a SIGSEGV. I checked that both still happens on master as > of today. The btrfs check crash is another matter. I've seen it crash many times, but the more recent versions are more reliable and haven't seen a crash lately. > I don’t know if this is relevant at all, but all the machines that failed > that way were used to run VMs with KVM/QEMU. DIsk activity tends to be > somewhat intense on occasions, since the VMs running there are part of a > personal Jenkins ring that automatically builds various projects. Nominally, > there are between three and five guests running (Windows XP, WIndows 10, > macOS, Fedora25, Ubuntu 16.04). I do run VM's quite often with all of my setups but rarely two concurrently and never three or more. So, hmmm. And are the VM's backed by a qemu image on Btrfs? Or LVM? -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
