This bug was fixed in the package mdadm - 4.1-2ubuntu3.2
---
mdadm (4.1-2ubuntu3.2) eoan; 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 from 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
** 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/1847924
Title:
Introduce broken state parsing to mdadm
To manage notifications about
** Tags removed: sts-sponsor-ddstreet
** Tags removed: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847924
Title:
Introduce broken state parsing to mdadm
To manage notifications
Thanks Dan and Łukasz - I've tested both Bionic
(4.1~rc1-3~ubuntu18.04.4) and Eoan (4.1-2ubuntu3.2) versions on
-proposed, following the test procedure suggest in the description -
both versions passed.
Cheers,
Guilherme
** Tags removed: block-proposed-bionic block-proposed-disco
Hello Guilherme, 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.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
re-uploaded the V3 to Bionic and Eoan, @rbasak @sil2100 does this change
address your concerns?
As this removes (comments out) the patches from bug 1850540, it no
longer needs to be blocked until a new kernel is released, as @gpiccoli
explains in comment 21.
--
You received this bug
** Patch added: "Eoan debdiff V3"
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1847924/+attachment/5320501/+files/lp-1847924-eoan_V3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi @ddstreet, thanks for the last upload and all the effort in this
case!
So, we had a situation in which LP #1850540 (the raid0 layout issue)
caused the mdadm package to stuck blocked in -proposed due to issues
with kernel. They're still figuring that out, so we (Dann, Stephan, from
kernel, and
Uploaded mdadm with V2 patches to B/D/E, however please note as I just
updated this bug description to explain, all future updates to mdadm are
now temporarily blocked due to the mdadm changes from bug 1850540
requiring corresponding kernel patches that are not yet released. I've
added the
Hi Robie and Łukasz, thanks again for your feedback and valid concerns.
I've just updated the LP with new debdiffs for the modified SRU patch -
this one won't change the mdadm behavior strictly more than necessary.
Basically, the code chunk added by this debdiff (in B/D/E) is:
++
** Patch added: "lp-1847924-disco_V2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1847924/+attachment/5311772/+files/lp-1847924-disco_V2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp-1847924-eoan_V2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1847924/+attachment/5311773/+files/lp-1847924-eoan_V2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp-1847924-bionic_V2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1847924/+attachment/5311771/+files/lp-1847924-bionic_V2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
in the meantime I'll reject the current uploads from confusing the SRU
folks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847924
Title:
Introduce broken state parsing to mdadm
To manage
Thanks a lot Robie and Łukasz, reasonable points! I'll work the new diff
for B/D/E and in parallel I'm trying the merge for Focal.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Robie asked me for a second opinion on this, so I had a look at it right
now. I must say that I'm a bit undecided here, similarly to Robie. But
with my SRU-hat on, first thing first: we should not introduce behavior
changes that can introduce regressions of existing tools without very
solid
I think you've hit the nail on the head with comment 9. That was exactly
my concern - thanks! I'm not sure I follow exactly the matrix of the set
of states before and after the patch and how the mapping should work in
option (b), but assuming that it does what I'm confident we both are in
Just a clarification comment - we're still discussing this (with Robie
and the server/foundations folks) , so it's not really ready for upload
since we may need a change in the patches for the current releases.
Thanks,
Guilherme
--
You received this bug notification because you are a member
Robie, I've just updated the description with more information on the
user impact (and why we should have this patch), and also the regression
potential.
I wasn't completely right in my last comment, sorry - for RAID0/Linear
arrays, the output of the array state in "mdadm --detail" may change
** Description changed:
[Impact]
* Currently, mounted raid0/md-linear arrays have no indication/warning
when one or more members are removed or suffer from some non-recoverable
error condition. The mdadm tool shows "clean" state regardless if a
member was removed.
* The patch
Hi Robie, thanks for you concerns! They are valid and make sense. Let me
first give you some context on why this is needed in stable releases:
the mdadm patch is a counter-part of a kernel modification which
performs 2 things: (a) 'broken' state when raid0/linear arrays have a
member missing; (b)
I think I understand the issue, but don't see a documented explanation
of why this needs to be added to stable Ubuntu releases.
What is the actual impact to users in not having mdadm able to pass
through this "broken" state information, please, and how would adding
this feature to stable releases
** 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/1847924
Title:
Introduce broken state parsing to mdadm
To manage notifications about this
uploaded to b/d/e, and i'll look at merging f next week and including
this patch.
** Tags added: sts-sponsor-ddstreet
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847924
Title:
Introduce broken
** Description changed:
[Impact]
* Currently, mounted raid0/md-linear arrays have no indication/warning
when one or more members are removed or suffer from some non-recoverable
error condition. The mdadm tool shows "clean" state regardless if a
member was removed.
* The patch
** Bug watch added: Debian Bug tracker #943520
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943520
** Also affects: mdadm (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943520
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Changed in: mdadm (Ubuntu Focal)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847924
Title:
Introduce broken state parsing to mdadm
To manage
** Also affects: mdadm (Ubuntu Ff-series)
Importance: Undecided
Status: New
** Changed in: mdadm (Ubuntu Ff-series)
Status: New => Confirmed
** Changed in: mdadm (Ubuntu Ff-series)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: mdadm (Ubuntu
Thanks @gpiccoli; I can't sponsor this now, since Eoan is in final
freeze, but once it's released I'll be happy to sponsor.
** Changed in: mdadm (Ubuntu Eoan)
Status: Confirmed => In Progress
** Changed in: mdadm (Ubuntu Disco)
Status: Confirmed => In Progress
** Changed in: mdadm
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847924
Title:
Introduce broken state parsing to mdadm
To manage notifications about this bug go to:
The attachment "lp-1847924-bionic.debdiff" seems to be a debdiff. The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag,
** Patch added: "lp-1847924-eoan.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1847924/+attachment/5296854/+files/lp-1847924-eoan.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp-1847924-disco.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1847924/+attachment/5296837/+files/lp-1847924-disco.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- TBD - will update soon the LP with details, for now it's just for the LP
- number.
+ [Impact]
+
+ * Currently, mounted raid0/md-linear arrays have no indication/warning
+ when one or more members are removed or suffer from some non-recoverable
+ error condition. The
36 matches
Mail list logo
