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

2017-03-27 Thread SW Riccardo Scartozzi
I've just had the chance to try again now. Sorry but I had to try on a different server. On 2017-03-24 12:02, Jarek Kamiński wrote: W dniu 24.03.2017 o 11:45, SW Riccardo Scartozzi pisze: On recent kernels it just works. Sorry but as said in my previous post I'm still experiencing the issue e

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

2017-03-24 Thread Jarek Kamiński
W dniu 24.03.2017 o 11:45, SW Riccardo Scartozzi pisze: >> On recent kernels it just works. > Sorry but as said in my previous post I'm still experiencing the issue > even with the kernel version 4.9 from backports. Have you tried creating the volume on 4.9, or just activating a previously-created

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

2017-03-24 Thread SW Riccardo Scartozzi
On recent kernels it just works. Sorry but as said in my previous post I'm still experiencing the issue even with the kernel version 4.9 from backports. I believe the bug can be closed now. Sorry, but the bug is still present! As Jarek Kamiński himself said: The legacy mirror is not affected

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

2017-03-24 Thread Jarek Kamiński
Hello, W dniu 22.03.2017 o 00:34, SW Riccardo Scartozzi pisze: > I was experiencing the same issue as describe in this bug report and, as > pointed by Harrison Metzger, the bug was probably introduced after > kernel 3.16-3-amd64 because for sure it was working until that version. > > I don't get

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

2017-03-21 Thread SW Riccardo Scartozzi
I was experiencing the same issue as describe in this bug report and, as pointed by Harrison Metzger, the bug was probably introduced after kernel 3.16-3-amd64 because for sure it was working until that version. I don't get what causes the problem. It could be interesting to test if the proble

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

2017-01-24 Thread Sebastian Bachmann
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:

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

2016-03-08 Thread Tomas Pazderka
Package: lvm2 Version: 2.02.142-1+b1 Followup-For: Bug #804629 Dear Maintainer, I am affected by this bug as well. Removing the mirroring from the failing LV allows mounting the volume. Adding the mirroring back works as well until next reboot. Best regards, Tomas -- System Information: Debia

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

2016-01-14 Thread Olaf Meeuwissen
Just FYI, this bug is still present with - linux-image-4.2.0-1-amd64 4.2.6-1 - linux-image-4.3.0-1-amd64 4.3.3-5 I've read through the thread and will take my system off LVM RAID1. I have submitted #811033 against lvm2, requesting this to be documented. Hope this helps, -- Olaf Meeuwissen, LP

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

2015-11-09 Thread Olaf Meeuwissen
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