Re: fdatasync semantics and block device backup

2020-04-28 Thread Kevin Wolf
Am 28.04.2020 um 15:58 hat Bryan S Rosenburg geschrieben: > Kevin Wolf wrote on 04/28/2020 07:11:24 AM: > > I think "don't do that" is a good answer actually. > > > > You may want to put an NBD indirection between QEMU and your object > > store, so that the close() syscall will just block a qemu-

RE: fdatasync semantics and block device backup

2020-04-28 Thread Bryan S Rosenburg
Kevin Wolf wrote on 04/28/2020 07:11:24 AM: > > Am 27.04.2020 um 21:49 hat Bryan S Rosenburg geschrieben: > > Blockdev community, > > > > Our group would like to write block device backups directly to an object > > store, using an interface such as s3fs or rclone-mount. We've run into > > pr

Re: fdatasync semantics and block device backup

2020-04-28 Thread Kevin Wolf
Hi Bryan, first of all, for your next question, please don't reply to a message in an unrelated thread, but start a new email. This will give you a lot more visibility because people generally use a threaded email view and will decide whether to read an email or not depending on whether the topic

fdatasync semantics and block device backup

2020-04-27 Thread Bryan S Rosenburg
Blockdev community, Our group would like to write block device backups directly to an object store, using an interface such as s3fs or rclone-mount. We've run into problems with both interfaces, and in both cases the problems revolve around fdatasync system calls. With s3fs, fdatasync calls are