On Sun, Mar 20, 2016 at 3:18 AM, Patrick Tschackert <Killing-Time@xxxxxx> wrote: > Thanks for answering again! > So, first of all I installed a newer kernel from the backports as per Nicholas D Steeves suggestion: > > $ apt-get install -t jessie-backports linux-image-4.3.0-0.bpo.1-amd64 > > After rebooting: > $ uname -a > Linux vmhost 4.3.0-0.bpo.1-amd64 #1 SMP Debian 4.3.5-1~bpo8+1 (2016-02-23) x86_64 GNU/Linux > > But the problem with mounting the filesystem persists :( > >> OK I went back and read this again: host is managing the md raid5, the >> guest is writing Btrfs to an "encrypted container" but what is that? A >> LUKS encrypted LVM LV that's directly used by Virtual Box as a raw >> device? It's hard to say what layer broke this. But the VM crashing is >> in effect like a power failure, and it's an open question (for me) how >> this setup deals with barriers. A shutdown -r now should still cleanly >> stop the array so I wouldn't expect there to be an array problem but >> then you also report a device failure. Bad luck. > > The host is managing an md raid 6 (/dev/md0), and I had an encrypted volume (via cryptsetup) on top of that device. > The host mounted the btrfs filesystem contained in that volume, and the VM wrote to the filesystem as well using a virtualbox shared folder. OK well to me the VM doesn't seem related off hand. Ultimately its only the host writing to the filesystem, even for the shared folder. The guest VM has no direct access to do Btrfs writes, it's something like a network-like shared folder. > After this, I think I'll just do away with the virtual machine on this host, as the app contained in that vm can also run on the host. > I tried to be fancy, and it seems to needlessly complicate things. virt-manager or gnome-boxes work better, although you lose shared folder, you'll have to come up with a work around, like using NFS. > $ for i in /sys/class/scsi_generic/*/device/timeout; do echo 120 > "$i"; done > (I know this isn't persistent across reboots...) Correct. -- Chris Murphy -- 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
