On Wed, 13 Nov 2019 21:45:13 + Jakob Haufe wrote:
> [...]
> Adding raid1 to /etc/initramfs/modules made my system boot.
>
> This suggests /usr/share/initramfs-tools/hooks/lvm2 might be at fault
here.
>
> I have to check whether this applies to bullseye/sid as well, but I
> guess it does.
I stumbled across this issue yet again in a fresh buster installation.
Various conversions did not solve it for me, but after reading [1], I
checked and found that my initramfs indeed did not contain raid1.ko.
Adding raid1 to /etc/initramfs/modules made my system boot.
This suggests
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
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
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
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
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
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:
It almost ruined my day, but the solution is simple: when creating the
mirror use "--mirrorlog mirrored --alloc anywhere".
In the case of a configured lvm mirror, you can follow a procedure like
this:
lvconvert -m 0
lvconvert -m 1 --mirrorlog mirrored --alloc anywhere
For example, in my case
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
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,
Package: linux-image-amd64
--- Please enter the report below this line. ---
Actually, after some research and having run dozens of old kernel versions I
came to the conclusion that this LVM/RAID1 shit NEVER WORKED PROPERLY.
It's just unbelievable. This RAID1 feature was added to LVM2 in 2011.
But then again, I guess md should get metadata from some backend provided by
lvm, not from the device directly? (Don't know for sure, didn't dive deep into
the driver yet.)
I'm having a very similar issue when I upgraded to a newer kernel. With the
older kernels I can still boot, but I think that is actually a bug. On the
old kernel, dmesg shows:
[ 244.454698] md/raid:mdX: device dm-88 operational as raid disk 3
[ 244.454810] md/raid:mdX: device dm-86 operational
Package: linux-image-amd64
Version: 4.2+68
--- Please enter the report below this line. ---
This seems to be a duplicate of #795772, which I've filed on src:linux months
ago. (I wonder why so little info on this bug available, like nobody else uses
LVM's RAID1 feature?)
--- System
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:
-
16 matches
Mail list logo
