** No longer affects: ubuntu-release-notes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849682
Title:
[REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with
default_layout setting
To man
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
Aha - found the curtin installation log - this proves the theory in the
previous comment:
Oct 24 00:03:33 akis cloud-init[2796]: mdadm detail scan after assemble:
Oct 24 00:03:33 akis cloud-init[2796]: ARRAY /dev/md/akis:0 level=raid0
num-devices=2 metadata=1.2 name=akis:0 UUID=01fd64cc:287c6b15:
In Comment #3, I noted that it was mysterious that we were seeing this
at all on the reported system - but, after staring at the log, I think
I've an explanation for that now.
This system is supposed to be configured to have 8 identical NVMe drives
in a raid0 mounted at /raid. There are also 2 oth
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Bug watch added: Debian Bug tracker #944676
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944676
** Also affects: mdadm (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944676
Importanc
This bug was fixed in the package linux - 4.15.0-69.78
---
linux (4.15.0-69.78) bionic; urgency=medium
* KVM NULL pointer deref (LP: #1851205)
- KVM: nVMX: handle page fault in vmread fix
* CVE-2018-12207
- KVM: MMU: drop vcpu param in gpte_access
- kvm: Convert kvm_l
This bug was fixed in the package linux - 5.0.0-35.38
---
linux (5.0.0-35.38) disco; urgency=medium
* [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout
setting (LP: #1849682)
- SAUCE: Fix revert "md/raid0: avoid RAID0 data corruption due to layout
This bug was fixed in the package linux - 5.3.0-22.24
---
linux (5.3.0-22.24) eoan; urgency=medium
* [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout
setting (LP: #1849682)
- Revert "md/raid0: avoid RAID0 data corruption due to layout confusion."
** Changed in: linux (Ubuntu Disco)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849682
Title:
[REGRESSION] md/raid0: cannot assemble multi-zone RAID0 w
I can 100% reproduce this on 5.0.0-34, but not at all on 5.0.0-32, so
marking verification-failed.
** Tags removed: verification-needed-disco
** Tags added: verification-failed-disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
The disco story is not so pretty:
[0.00] Linux version 5.0.0-34-generic (buildd@lgw01-amd64-051) (gcc
version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #36~18.04.1-Ubuntu SMP Wed Oct
30 08:08:56 UTC 2019 (Ubuntu 5.0.0-34.36~18.04.1-generic 5.0.21)
[0.00] Command line: BOOT_IMAGE=/bo
= Verification =
I see 2 pieces to this:
1) The original report, in Comment #1, where the offending patch caused an
issue on a system where it shouldn't have - i.e., a raid0 w/ homogenous member
sizes. We were never able to reproduce this in subsequent tests w/ the patch
applied. I know sfeole
@dannf: Ping for verification :)
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849682
Title:
[REGRESSION] md/ra
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag 'verificati
** Description changed:
+ This bug tracks the temporary revert of the upstream fix for a
+ corruption issue. Bug 1850540 tracks the re-application of that fix once
+ we have a full solution.
+
Users of RAID0 arrays are susceptible to a corruption issue if:
- The members of the RAID array are
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849682
Title:
[REGRESSION] md/raid0: cannot assemble multi-zone RAID0 w
I've proposed changing the error message to point to a webpage w/ a better
explanation:
https://marc.info/?l=linux-raid&m=157196348406853&w=2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849682
T
** Description changed:
Users of RAID0 arrays are susceptible to a corruption issue if:
- The members of the RAID array are not all the same size[*]
- Data has been written to the array while running kernels < 3.14 *and* >=
3.14.
- Upstream is dealing with this by adding a versioned la
** Description changed:
Users of RAID0 arrays are susceptible to a corruption issue if:
- - The members of the RAID array are not all the same size[*]
- - Data has been written to the array while running kernels < 3.14 and >=
3.14.
+ - The members of the RAID array are not all the same size[
** Description changed:
- [Impact]
- After installing the 4.15.0-67.76 kernel from bionic-proposed, our Nvidia
DGX2 system is no longer bootable.
+ Users of RAID0 arrays are susceptible to a corruption issue if:
+ - The members of the RAID array are not all the same size[*]
+ - Data has been wr
OK - this is a messy one. It is due to the backport of this:
https://github.com/torvalds/linux/commit/c84a1372df929033cb1a0441fb57bd3932f39ac9
Reverting that is probably not the right answer because the point of it
is to avoid corruption. But this is a pretty serious usability issue. It
is not at
22 matches
Mail list logo
