New kernel 4.8 killed dm raid?

robc · 2016-10-22 05:15:31

I just upgraded and the new kernel is prevented my LVM array from starting up:

Unable to assemble array: Unknown flag(s) in compatible feature flags

They appeared to submit a kernel patch for it: https://patchwork.kernel.org/patch/9371273/

I'm using LVM, it sounds like I might be able to recreate the array, but I'm going to have to update my boot stick with the 4.8 kernel so the flags are set correctly? I guess I'll patch if I have to...

jasonwryan · 2016-10-22 19:44:47

I have had no issue with any of the 4.8.x series kernels, running LVM on LUKS on RAID1.

graysky · 2016-10-22 20:02:47

4.8.x for my RAID is fine but I haven't tried to create one, just use an existing array.

richli · 2016-10-22 21:31:08

I've been hit this problem, too. For the record, I'm not using LVM on top of mdadm, but am using a mirrored logical volume.

graysky · 2016-10-22 22:09:57

I'll bet if you boot into the lts kernel, build your raid, then boot into the mainline kernel it will work just fine.

frostschutz · 2016-10-22 22:35:02

few people use dmraid/lvmraid, apparently it was noticed too late...

stick to old kernel until grass grows out of it

loqs · 2016-10-22 22:55:24

frostschutz wrote:

stick to old kernel until grass grows out of it

You mean the lts one correct not linux-4.7.6-1 which does not contain a backported version of 19be0eaffa3ac7d8eb6784ad9bdbc7d67ed8e619

robc · 2016-10-23 00:00:18

The latest 4.7 works for me... linux-4.7.6-1 (sorry not on box)? it was just the leap to 4.8 that killed it for me. If it helps I'm LUKS on an LMV mirror.

richli · 2016-11-10 18:19:35

It looks like version 4.8.7 contains the fix? From https://cdn.kernel.org/pub/linux/kernel … eLog-4.8.7:

commit 6e5456768ba1ee581f8e43c8f90296ead4c30b98
Author: Andy Whitcroft <apw@canonical.com>
Date: Tue Oct 11 15:16:57 2016 +0100
dm raid: fix compat_features validation

commit 5c33677c87cbe44ae04df69c4a29c1750a9ec4e5 upstream.

In ecbfb9f118bce4 ("dm raid: add raid level takeover support") a new
compatible feature flag was added. Validation for these compat_features
was added but this only passes for new raid mappings with this feature
flag. This causes previously created raid mappings to be failed at
import.

Check compat_features for the only valid combination.

Fixes: ecbfb9f118bce4 ("dm raid: add raid level takeover support")
Signed-off-by: Andy Whitcroft <apw@canonical.com>
Signed-off-by: Heinz Mauelshagen <heinzm@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Here's the commit: https://git.kernel.org/cgit/linux/kerne … ead4c30b98

Arch Linux

#1 2016-10-22 05:15:31

New kernel 4.8 killed dm raid?

#2 2016-10-22 19:44:47

Re: New kernel 4.8 killed dm raid?

#3 2016-10-22 20:02:47

Re: New kernel 4.8 killed dm raid?

#4 2016-10-22 21:31:08

Re: New kernel 4.8 killed dm raid?

#5 2016-10-22 22:09:57

Re: New kernel 4.8 killed dm raid?

#6 2016-10-22 22:35:02

Re: New kernel 4.8 killed dm raid?

#7 2016-10-22 22:55:24

Re: New kernel 4.8 killed dm raid?

#8 2016-10-23 00:00:18

Re: New kernel 4.8 killed dm raid?

#9 2016-11-10 18:19:35

Re: New kernel 4.8 killed dm raid?

Board footer