kernel-packages team mailing list archive

[Stefan Bader <stefan.bader@xxxxxxxxxxxxx>]

Right now 3.17-rc1 would show the virtio related issue only. With the current 3.16 we have there is still the writeback hung task issue mingled in (except with a kernel version of 3.16.0-10.15 or later), see bug #1357295.
Using Xen paravirt drives, there is no crash. This hints that it is something directly related to the combination of virtio disks and bcache. This looks to be an upstream problem still. So for this bug we should concentrate on either 3.17 or the latest Utopic kernel.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1359146

Title:
  Kernel crash when mounting bcache on a vm with virtio

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  bcache used in a virtual machine:

  If you create a bcache device with caching device and backing device
  on virtio disks, it will let you do your work until you mount it where
  it crashes the virtual machine (virtual machine is utopic, host is
  trusty).

  For example:
  if your backing device is /dev/vdb, and your caching device is /dev/vdc:

  sudo make-bcache -B /dev/vdc -C /dev/vdb --writeback
  is ok

  mkfs.ext4 /dev/bcache0 -L bcache-test
  is ok

  but
  mount /dev/bcache0 /media/bcache

  make it crash, if I remember well one time I had a few seconds before
  crash, but I don't have any log files.

  qemu-system-x86 is version 2.0.0+dfsg-2ubuntu1.2

  Re-installing, and using IDE virtual interface seems to create and
  mount the bcache device is ok.

  After bcache created an mounted successfully with IDE interfaces,
  switching to SATA, SCSI, and USB with booting and mounting seemed ok.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359146/+subscriptions