Ubuntu 19.10 (Eoan Ermine) has reached end of life, so this bug will not
be fixed for that specific release.
** Changed in: mdadm (Ubuntu Eoan)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: ubuntu-release-notes
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850540
Title:
multi-zone raid0 corruption
To manage notifications about this bug g
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: mdadm (Ubuntu Precise)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: linux (Ubuntu Precise)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Changed in: linux (Ubuntu Disco)
Status: Fix Committed => Won't Fix
** Changed in: mdadm (Ubuntu Disco)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
This bug was fixed in the package linux - 5.4.0-18.22
---
linux (5.4.0-18.22) focal; urgency=medium
* focal/linux: 5.4.0-18.22 -proposed tracker (LP: #1866488)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
* Add sysf
This bug was fixed in the package linux - 4.4.0-174.204
---
linux (4.4.0-174.204) xenial; urgency=medium
* xenial/linux: 4.4.0-174.204 -proposed tracker (LP: #1861122)
* Xenial update: 4.4.211 upstream stable release (LP: #1860681)
- hidraw: Return EPOLLOUT from hidraw_poll
This bug was fixed in the package linux - 4.15.0-88.88
---
linux (4.15.0-88.88) bionic; urgency=medium
* bionic/linux: 4.15.0-88.88 -proposed tracker (LP: #1862824)
* Segmentation fault (kernel oops) with memory-hotplug in
ubuntu_kernel_selftests on Bionic kernel (LP: #186231
This bug was fixed in the package linux - 5.3.0-40.32
---
linux (5.3.0-40.32) eoan; urgency=medium
* eoan/linux: 5.3.0-40.32 -proposed tracker (LP: #1861214)
* No sof soundcard for 'ASoC: CODEC DAI intel-hdmi-hifi1 not registered' after
modprobe sof (LP: #1860248)
- ASoC:
= linux/eoan verification =
I created a multi-zone array on current eoan, then upgraded to the -proposed
kernel:
[4.021562] md/raid0:md0: !!! DEFAULTING TO ALTERNATE LAYOUT !!!
[4.021563] md/raid0: Please set raid0.default_layout to 1 or 2
[4.021564] md/raid0: Read the following page
** Tags removed: verification-done verification-done-bionic
verification-done-disco verification-done-eoan
** Tags added: verification-needed verification-needed-bionic
verification-needed-disco verification-needed-eoan
** Tags removed: block-proposed-bionic block-proposed-disco block-
proposed-
This bug was fixed in the package mdadm - 4.1~rc1-3~ubuntu18.04.4
---
mdadm (4.1~rc1-3~ubuntu18.04.4) bionic; urgency=medium
* Introduce "broken" state for RAID0/Linear in mdadm (LP: #1847924)
- d/p/lp1847924-Introduce-new-array-state-broken-for-raid0.patch
* Disable patches
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-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Xenial)
Status: Conf
** Changed in: linux (Ubuntu Trusty)
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/1850540
Title:
multi-zone raid0 corruption
To manage notifications about
The following patches sent on 2019/12/18 have been removed from the
Eoan/Disco/Bionic kernels:
https://lists.ubuntu.com/archives/kernel-team/2019-December/106461.html
Therefore I'm setting the linux tasks back to 'In Progress'.
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed =>
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Disco)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Eoan)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a membe
Adding the block-proposed-* tags as per comment #11.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-disco verification-needed-eoan
** Tags added: block-proposed-bionic block-proposed-disco block-proposed-eoan
verification-done verification-done-bionic verific
There is no plan to reapply the kernel side of these fixes ahead of
18.04.4. Introducing the mdadm side of that in 18.04.4 therefore would
cause a regression in functionality:
ubuntu@ip-172-30-0-208:~$ sudo mdadm --create /dev/md0 --run
--metadata=default --level=0 --raid-devices=2 /dev/xvdb /dev/
= bionic verification =
ubuntu@ip-172-30-0-117:~$ sudo mdadm --create /dev/md0 --run --metadata=default
--level=0 --raid-devices=4 /dev/xvdb /dev/xvdc /dev/xvdd /dev/xvde
mdadm: array /dev/md0 started.
ubuntu@ip-172-30-0-117:~$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1]
** Tags removed: verification-needed-disco
** Tags added: verification-done-disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850540
Title:
multi-zone raid0 corruption
To manage notifications ab
= disco verification =
ubuntu@ip-172-30-0-118:~$ sudo mdadm --create /dev/md0 --run --metadata=default
--level=0 --raid-devices=2 /dev/xvdb /dev/xvdc
mdadm: Fail create md0 when using /sys/module/md_mod/parameters/new_array
mdadm: array /dev/md0 started.
ubuntu@ip-172-30-0-118:~$ cat /proc/mdstat
= eoan verification =
ubuntu@ip-172-30-0-147:~$ sudo mdadm --create /dev/md0 --run --metadata=default
--level=0 --raid-devices=2 /dev/xvdb /dev/xvdc
mdadm: Fail create md0 when using /sys/module/md_mod/parameters/new_array
mdadm: array /dev/md0 started.
ubuntu@ip-172-30-0-147:~$ cat /proc/mdstat
Hello dann, or anyone else affected,
Accepted mdadm into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mdadm/4.1-1ubuntu1.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubu
Hello dann, or anyone else affected,
Accepted mdadm into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mdadm/4.1-2ubuntu3.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubun
** Description changed:
Bug 1849682 tracks the temporarily revert of the fix for this issue,
while this bug tracks the re-application of that fix once we have a full
solution.
- Fix checklist:
- [ ] Restore c84a1372df929 md/raid0: avoid RAID0 data corruption due to layout
confusion.
- [
This bug was fixed in the package mdadm - 4.1-4ubuntu1
---
mdadm (4.1-4ubuntu1) focal; urgency=medium
[ dann frazier ]
* Merge from Debian unstable. Remaining changes:
- Ship finalrd hook.
- Do not install mdadm-shutdown.service on Ubuntu.
- Drop broken and unused ini
** Changed in: mdadm (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850540
Title:
multi-zone raid0 corruption
To manage notifications about this bug go t
** Changed in: mdadm (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850540
Title:
multi-zone raid0 corruption
To manage notifications about this bug go to:
ht
** 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
Importance: Unknown
Status: Unknown
** Also affects: ubuntu-release-notes
Importa
mdadm patches are under review upstream:
https://marc.info/?l=linux-raid&m=157247979712647&w=2
** Changed in: mdadm (Ubuntu Focal)
Status: New => Confirmed
** Changed in: mdadm (Ubuntu Eoan)
Status: New => Confirmed
** Changed in: mdadm (Ubuntu Disco)
Status: New => Confir
** Description changed:
Bug 1849682 tracks the temporarily revert of the fix for this issue,
while this bug tracks the re-application of that fix once we have a full
solution.
+
+ Fix checklist:
+ [ ] Restore c84a1372df929 md/raid0: avoid RAID0 data corruption due to layout
confusion.
+ [
** Description changed:
Bug 1849682 tracks the temporarily revert of the fix for this issue,
while this bug 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 not all
I've nominated mdadm for this issue as well because it currently does not:
1) Let you create a new raid0 array w/o first setting a default_layout, which
will regress behavior in installers, etc.
2) save the layout version in the raid config, so you need to set
default_layout - or set individu
34 matches
Mail list logo
