Fully Inconsistent volumes should allow access
Bug #1430698 reported by
Philipp Marek
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| drbd9 |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
Volumes that are "Inconsistent" on all nodes should allow access to them *without* needing "drbdadm primary --force".
That would eg. allow a "mkfs", "blkdiscard", or other initializing requests.
"drbdadm primary --force" might be harmful if other volumes in the same resource are in a non-optimal state, ie. "OutDated", "Inconsistent", detached, etc.
Easiest way to test that:
* "drbdmanage nv foo 4m --deploy 2"
* wait a bit
* "drbdmanage nv foo 4m"
* Now the resource has one "UpToDate" volume and the other one is "Inconsistent".
| Changed in drbd9: | |
| milestone: | none → 9.0.0 |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
To post a comment you must log in.
