On Thu, 4 May 2017, qi Shi wrote: > when bluestore bigwrite it divided into two steps: > 1, alloc a disk space and write data to it. > 2, update the metadata to the database(rocksdb). > > How to do data consistency? > > Will the following error occur? > when write data to device sucess Osd process crushed . > But metadata is not update to rocksdb. > > So I think there are legacy data in the disk,this can cause data > inconsistencies. New data is always written to unused, unallocated space. And the metadata that points to it is always committed after those writes are completed and flushed to the device. If you crash in between, it just means the empty space has different garbage than it had before. sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
