Bug 244693 - gmirror configure priority does not take an effect until reboot?
Summary: gmirror configure priority does not take an effect until reboot?
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 12.1-RELEASE
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-geom (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-09 12:05 UTC by Paul
Modified: 2020-10-29 02:26 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul 2020-03-09 12:05:32 UTC 
`gmirror label -hvb prefer test /dev/gpt/test1 /dev/gpt/test2`

gmirror sets priority by default:
/dev/gpt/test1 -> 0
/dev/gpt/test2 -> 1

when you run `dd if=/dev/mirror/test of=/dev/null` you can see in gstat/iostat, that /dev/gpt/test2 is loaded for read.

then after `gmirror configure -p 5 test /dev/gpt/test1`, running `dd if=/dev/mirror/test of=/dev/null`  you can see, that /dev/gpt/test2 is still used for read.

after reboot, changes take effect, and /dev/gpt/test1 really starts to be used for read operations.

there are no way to reload gmirror to apply changes without reboot, except this strange way, when you remake mirror with the "right" devices order:
`gmirror stop test; gmirror label -hvb prefer test /dev/gpt/test2 /dev/gpt/test1`