Bug#804629: linux-image-amd64: Cannot mount LVM RAID1 file system at boot

[Olaf Meeuwissen <olaf.meeuwissen@avasys.jp>]

Package: linux-image-amd64
Version: 4.2+68
Severity: important

Dear maintainer(s),

I recently put one of my file systems on LVM RAID1.  All is fine when I
lvconvert or lvcreate the RAID1 mirror on a running kernel.  The problem
happens when I reboot the system.  This happens with:

 - linux-image-4.2.0-1-amd64  4.2.5-1
 - linux-image-4.1.0-2-amd64  4.1.6-1
 - linux-image-4.1.0-1-amd64  4.1.3-1

Rebooting with a linux-image-4.0.0-2-amd64 (4.0.8-2) kernel works fine.
The LVM RAID1 file system mounts automatically and is fully usable.

During the failing boots I see:

  Setting up LVM Volume Groups...  lvmetad is not active yet, using direct activation during sysin
it
    device-mapper: reload ioctl on (253:8) failed: Invalid argument

and a little later:

  fsck.ext4: No such file or directory while trying to open /dev/mapper/helix-srv
  Possibly non-existent device?

Trying to activate the LV after the boot does not work either.

  # lvchange -ay helix/srv
    device-mapper: reload iocth on (253:8) failed: Invalid argument

In my syslog I see:

  mdX: invalid bitmap file superblock: bad magic
  mdX: bitmap file superblock
           magic: 00000401

and

  mdX: failed to create bitmap (-22)
  device-mapper: table: 253:8 raid: Fail to run raid araay

I have found https://bugzilla.kernel.org/show_bug.cgi?id=100491[1][1] which
mentions some of the messages I observe.  I do not get the OOPS but it
might be related.

For the time being I'll stick to 4.0.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages linux-image-amd64 depends on:
ii  linux-image-4.2.0-1-amd64  4.2.5-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information

Hope this helps,
-- 
Olaf Meeuwissen, LPIC-2     EPSON FLOSS Engineer -- AVASYS CORPORATION
FSF Associate Member #1962               Help support software freedom
                 http://www.fsf.org/jf?referrer=1962