Re: [Nbd] NBD_CMD_FLAG_FUA?
- To: Alex Bligh <alex@...872...>
- Cc: Nbd-general@lists.sourceforge.net
- Subject: Re: [Nbd] NBD_CMD_FLAG_FUA?
- From: Folkert van Heusden <folkert@...421...>
- Date: Fri, 9 Sep 2011 15:19:41 +0200
- Message-id: <CAFDOyVBLTpFtstrhwK2mJ8hZ1X90F0mxUwYLZaRDsE+V1TM23w@...18...>
- In-reply-to: <3DDB291606C4D2E41662C17A@...874...>
- References: <CAFDOyVDG+nL8O4QGArpoZ4Y01HxsS7ENkWhTHWMFq54y1k+gjA@...18...> <3DDB291606C4D2E41662C17A@...874...>
>> +bit 3 - NBD_FLAG_SEND_FUA
>> - does it mean that if bit 16 bit is set, NBD_CMD_FLAG_FUA should be
>> performed? - what on earth is NBD_CMD_FLAG_FUA for? what should I do if i
>> receive that message?
>
> You can't "perform" an NBD_CMD_FLAG_FUA, it's saying that the
> command to which it is attached (which, as per above, is NBD_CMD_WRITE
> only at the moment, though we'd also want to allow it on the
> recent NBD_CMD_DISCARD), you treat the command as having "force
> unit access" set, which means you should not acknowledge the
> command as complete until the data is written to the physical disk. IE
> it has the same semantics as the Linux block layer flag.
But isn't it the same as sending a NBD_CMD_FLUSH after a write/discard?
(thanks for the reply by the way!)
Folkert.
Reply to: