Distributed Network Block Device 3 --rewrite for Kernel 3.x https://git.openslx.org/dnbd3.git/atom/src/shared/protocol.h?h=v2.2 2019-07-23T15:24:27+00:00 2019-07-23T15:24:27+00:00 Simon Rettberg 2019-07-23T15:21:29+00:00 urn:sha1:a61b4f18a1f9dcb78dba4bcde48a9318b04a45ec This makes the server not set the FLAGS8_SERVER flag when establishing an uplink connection. Useful mostly for running a proxy on localhost for local caching. 2018-11-16T09:42:22+00:00 Simon Rettberg 2018-11-16T09:42:22+00:00 urn:sha1:a28448bce13f0d3c71e0b11e3d7c33663d1a2ee9 _backgroundReplication was still treated as a boolean flag, so a server with BGR_NONE would reject a server with BGR_HASHBLOCK. While this still forces the BGR_NONE proxy to replicate more than it normally would, it seems reasonable to allow this. 2018-04-05T16:31:22+00:00 Simon Rettberg 2018-04-05T16:31:22+00:00 urn:sha1:de824f77fcf7a9164d0e52cf9979c285174426db 2017-11-02T12:41:35+00:00 Simon Rettberg 2017-11-02T12:41:35+00:00 urn:sha1:1587f73c38c9228a1a93889aae6351eff891cbe8 Introduce new flag in "select image" message to tell the uplink server whether we have background replication enabled or not. Also reject a connecting proxy if the connecting proxy uses BGR but we don't, as this would basically force the image to be replicated locally too. 2017-10-24T09:27:44+00:00 Simon Rettberg 2017-10-24T09:27:44+00:00 urn:sha1:a0fbfe1c6d6f42b4c2704c882beda1c4cafe5016 2017-10-17T10:08:55+00:00 Simon Rettberg 2017-10-17T10:08:55+00:00 urn:sha1:102705470366b871109d2c3bf182c151ab71eb01 We steal 8 bits from the request offset to count hops when requests get relayed by proxies. This still leaves plenty of bits for the offset (56 bits, supporting images of up to 72 petabytes). This is used to detect proxy cycles. The algorithm is not perfect but should prevent endless relays of the same request. This is backwards compatible to old clients and servers, as the server only ever sets the hopcount in relayed requests if the upstream server is using protocol version 3 or newer, and clients are automatically upwards compatible as there is practically no image larger than 74PB, so the newly introduced hop count field is always 0 even in requests from old clients. 2016-03-22T14:58:13+00:00 Simon Rettberg 2016-03-22T14:58:13+00:00 urn:sha1:549a53070ae03b47e11943727afe4f8927cb6c42 2016-02-10T23:09:39+00:00 Sebastian 2016-02-10T20:53:15+00:00 urn:sha1:1ee67aedd55b452c7d5851d0e39e01aef4aca766 2016-02-01T11:41:11+00:00 Simon Rettberg 2016-02-01T11:41:11+00:00 urn:sha1:81c9da3c9d55fab13ab9a912cade320015d01613 This was a wrong decision made long time ago, and it's broken in certain scenarios (eg. two servers serving from same NFS mount). Also it's of limited use anyways since it only supportes ASCII and would ignore umlauts, so blöd and BLÖD would still be considered two different images. So if you relied on this "feature" in any way, be careful when updating. 2015-12-01T12:38:10+00:00 Simon Rettberg 2015-12-01T12:38:10+00:00 urn:sha1:ecc6e5dd28821bf1c207e074f1b5903426a7e4c4