Bug 545494
Summary: | Kernel Raid-1 support and mdadm could use a mark-as-synced switch | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Odin Trisk <fedora-bugzilla-odin> |
Component: | mdadm | Assignee: | Doug Ledford <dledford> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 12 | CC: | dledford |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-12-08 18:03:32 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Odin Trisk
2009-12-08 17:37:12 UTC
mdadm already has such a switch: --assume-clean It is, however, not advised even for raid1 arrays. While it is technically true that any unwritten portions of the disk have no guarantee of a consistent data state, the principal of least surprise suggests that we would want our raid arrays to behave like individual disks. Even in the uninitialized portions of a regular disk, the one thing that's true is from read to read, the data doesn't change. If we didn't sync the raid1 arrays, we would not provide that same behavior. |