kernel-packages team mailing list archive

[Tapani Tarvainen <ubuntu@xxxxxxxxxxxxxxxxxxxxx>]

I'll try to reproduce the bug with a bit smaller data set first (and
non-production data), as testing this with the real thing takes rather
too long (about two days per test). Also, I haven't yet determined if
this resulted in data corruption (I will, by comparing data with backup,
but it will also take several days).

(I assume I can ignore the apport-collect request by robot - if the
apport-cli output isn't sufficient, let me know. The machine is
headless, however, so running apport-collect is a bit difficult.)

-- 
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/1382335

Title:
  mdadm+lvm+cryptsetup+big disks: "bio too big device"

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I installed two new 6TB disks (WD Red) as RAID1 and pmove'd stuff over from old
  5x3TB RAID10 array to it (actually the move is still in progress, going to take some
  17 hours or so) and I get lots of these (4971 so far) in dmesg:

  [58693.807553] bio too big device dm-7 (664 > 8)
  [58694.037060] bio too big device dm-7 (1024 > 8)

  Looks like an old kernel bug that was supposedly fixed in 2012:
  https://lkml.org/lkml/2012/10/15/398

  The LV that apparently triggered that is 3TB in size (90% full) and
  encrypted with cryptsetup.

  I don't know if this is reproducible but I can try - it'd just take some
  two days every time (starting with restoring 3TB from backup).

  Ubuntu 14.04.1, 3.13.0-37-generic x86_64 kernel,
  Intel DQ57TM mobo, LSI 9211-8i SAS/SATA controller.

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