Date: Mon, 09 Mar 2020 12:05:32 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 244693] gmirror configure priority does not take an effect until reboot? Message-ID: <bug-244693-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244693 Bug ID: 244693 Summary: gmirror configure priority does not take an effect until reboot? Product: Base System Version: 12.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: spy@spy.zp.ua `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` -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-244693-227>