Juergen Fitschen posted on Thu, 05 Feb 2015 00:05:33 +0100 as excerpted: > I just got a deadlock on Linux 3.18.5. [...] > I am using a freshly installed Ubuntu 14.04 in a virtual machine. The > block device used for btrfs is a LVM volume offered by the KVM > hypervisor. > Unfortunately I was using an old version of my user space tools (Version > 3.12-1), so it might be related to that?
I know little to nothing about the complexities of btrfs in a VM so won't attempt an answer there. But about userspace specifically I can say this... For normal operation, btrfs userspace doesn't matter so much. It's the kernel that's vital as userspace mostly simply tells the kernel what to do at a relatively high level (mount/umount/snapshot/delete-snapshot/etc) and the kernel code handles pretty much everything at the more critical lower levels. OTOH, if there are problems and you are trying to fix them using userspace tools such as btrfs check, restore, etc, /that/ is when the /userspace/ version needs to be current, as it's then userspace doing the low-level stuff as well. Since it was during normal operations that this deadlock occurred, it's almost certainly a kernel problem (unless the problem is ultimately traced to a bug in the original mkfs.btrfs that created the filesystem, or the like), and that was current, so it's it's a current problem. =:^( Hopefully a dev or other regular with more VM experience will be along to help you further, but I could deal with this much, so I did. =:^) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
