nbd
nbd copied to clipboard
Merovius
Go implementation of Linux Network Block Devices
When connecting with `lo` and killing the process (via SIGINT or SIGTERM) it doesn't clean up the nbd-node, even though it could.
Relevant spec values: * NBD_FLAG_SEND_CACHE * NBD_CMD_CACHE
Blocked by #6. Relevant spec values: * NBD_OPT_SET_META_CONTEXT * NBD_OPT_LIST_META_CONTEXT * NBD_CMD_BLOCK_STATUS * NBD_REPLY_TYPE_BLOCK_STATUS * NBD_STATE_HOLE * NBD_STATE_ZERO * NBD_CMD_FLAG_REQ_ONE
Relevant spec values: * NBD_CMD_WRITE_ZEROES * NBD_FLAG_SEND_WRITE_ZEROES
When the server is shutting down (by a cancelled context) it shouldn't just abort handling requests, but instead reply to them with ESHUTDOWN or NBD_REP_ERR_SHUTDOWN, until the client disconnects. This...
Relevant spec values: * NBD_FLAG_SEND_TRIM * NBD_CMD_TRIM
Blocking #10 * NBD_OPT_STRUCTURED_REPLY * NBD_REPLY_FLAG_DONE * NBD_REPLY_TYPE_NONE * NBD_REPLY_TYPE_OFFSET_DATA * NBD_REPLY_TYPE_OFFSET_HOLE * NBD_REPLY_TYPE_ERROR * NBD_REPLY_TYPE_ERROR_OFFSET * NBD_STRUCTURED_REPLY_MAGIC * NBD_REPLY_FLAG_DONE * NBD_CMD_FLAG_DF * NBD_CMD_FLAG_NO_HOLE
The server should derive correct flags from the optional interfaces the Device supports (as well as the features we have implemented). Relevant spec values: * NBD_FLAG_HAS_FLAGS (should always be set)...
The convenience function `nbd.Loopback` does not yet allow to pass in a preferred block size. It would make sense to allow that - an `*os.File` backend for example, could derive...