Dear maintainer(s) and users affected by this bug, I was affected by this bug as well. The lvm was created as: lvcreate --type raid1 --name foo -L 50G bar with kernel 3.16.36-1+deb8u2 (yesterday).
After an upgrade to 3.16.39-1 (today), the volume would not activate: [ 50.848231] md/raid1:mdX: active with 2 out of 2 mirrors [ 50.850482] mdX: invalid bitmap file superblock: bad magic [ 50.851611] mdX: bitmap file superblock: [ 50.851613] magic: 55555555 [ 50.851615] version: 1431655765 [ 50.851616] uuid: 55555555.55555555.55555555.55555555 [ 50.851618] events: 134 [ 50.851619] events cleared: 134 [ 50.851620] state: 00000000 [ 50.851621] chunksize: 524288 B [ 50.851622] daemon sleep: 5s [ 50.851623] sync size: 52428800 KB [ 50.851624] max write behind: 0 [ 50.851627] mdX: failed to create bitmap (-22) [ 50.852809] device-mapper: table: 253:26: raid: Fail to run raid array [ 50.853940] device-mapper: ioctl: error adding target to table There was a second lv (also a --type raid1, but created earlier), that had some similar issue, but I was able to activate it partialy by using lvchange -a y --activationmode partial bar/otherfoo The other LV was not able to be activated even as degraded, thus I decided to rsync all files from one of the rimages and create a new one... HTH! regards sebastian
signature.asc
Description: OpenPGP digital signature
