Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #980881
| From | Dan Streetman <dan.streetman@canonical.com> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#943520: mdadm: Introduce broken state parsing to mdadm |
| Date | 2019-10-25 20:50 +0200 |
| Message-ID | <yVcOS-4MP-11@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
Package: mdadm
Version: 4.1-2
Severity: normal
Tags: patch
User: ubuntu-devel@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch
Dear Maintainer,
* 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 proposed in this SRU addresses this issue by introducing a new state "broken", which is analog to "clean" but indicates that array is not in a good/correct state. The commit, available upstream as 43ebc910 ("mdadm: Introduce new array state 'broken' for raid0/linear") [0], was extensively discussed and received a good amount of reviews/analysis by both the current mdadm maintainer as well as an old maintainer.
* One important note here is that this patch requires a counter-part in the kernel to be fully functional, which was SRUed in LP: #1847773.
It works fine/transparently without this kernel counter-part though.
In Ubuntu, the attached patch was applied to achieve the following:
* Introduce "broken" state for RAID0/Linear in mdadm (LP: #1847924)
Thanks for considering the patch.
Back to linux.debian.bugs.dist | Previous | Next | Find similar | Unroll thread
Bug#943520: mdadm: Introduce broken state parsing to mdadm Dan Streetman <dan.streetman@canonical.com> - 2019-10-25 20:50 +0200
csiph-web