mirror of
https://github.com/versity/scoutfs.git
synced 2026-09-23 00:14:22 +00:00
Auke Kok
81c6cf452b
I thought this would just work between ipv4 and ipv6 based quorum members, but it turns out it will only work one way by default. While we could make this work (multiple sockets, special sockopts) it is highly unlikely and very undesirable. Much stronger feels to just disallow it explicitly and reject mixed v4/v6 configurations outright (mkfs/change-quorum, and mount) to avoid this. I can't imagine this doing any good for users' fencing setups. The test cases added validate the 2 easy userspace checks. The mount check isn't easily testable because we disallow userspace from creating such a failure path. One additional test section tests the migration path from v4->v6->v4 so there's at least some test that checks that this actually works. Signed-off-by: Auke Kok <auke.kok@versity.com>
8 lines
270 B
Plaintext
8 lines
270 B
Plaintext
== mkfs rejects mixed v4/v6 quorum
|
|
rc: 64
|
|
== mkfs all-v4, mount three members, cross-mount signature visible
|
|
== change-quorum-config rejects mixed v4/v6 quorum
|
|
rc: 64
|
|
== switch v4 -> v6, signature survives, cross-mount write again
|
|
== switch v6 -> v4, signatures survive
|