Bug#664088: mdadm fails to initialize components for bitmap

[Markus Hochholdinger]

Hello karme,

Am 13.04.2012 um 13:56 Uhr schrieb karme at karme.de:
> I see the same? / similar problems. I removed the internal bitmap by
> accident. First I couldn't add a internal bitmap anymore later i got a
> kernel panic.

for me, adding the bitmap works, but the kernel crashes afterwards. After 
rebooting the machine, the raid1 has a bitmap, but will do (need) a complete 
rebuild.


> Didn't have the time to really inspect this but found this one regarding
> the kernel bug part:
> http://www.spinics.net/lists/raid/msg37940.html
> myself using kernel:
> ii  linux-image-3.2.0-2-amd64                3.2.12-1
> Linux 3.2 for 64-bit PCs
> greetings,
> karme
> PS: i think this is a regression

Yeah, I think also this is a regression. I'm using raid1 bitmaps, including 
removing and adding bitmaps for raid1 resizing, more than 5 years without 
problems. The crash is a kernel bug, but is triggered with mdadm from wheezy.


> PPS: would really help me if this gets fixed as i rely on the bitmap
> feature to sync my laptop to an external usb disk before leaving home

If you use a older version of mdadm, it shouldn't crash the kernel.


-- 
greetings

eMHa
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20120413/670a8625/attachment.pgp>