Tomasz Zawadzki 79006b9e56 blob: fix sequentially allocated clusters starting from 0 ... When serializing extents, run-length encoding is supposed to 1) RLE all sequential LBAs 2) RLE zero LBAs (unallocated) There is one special case, with sequential LBAs that start with 0 LBA. This is RLE as 1) case, but results in descriptor matching case 2). Which causes loss of allocated clusters. This requires following conditions to be met: - blobstore has just a single cluster reserved for MD - blob is thin provisioned - first allocation occurs on cluster_num=1 For last part to be true, very first write for blob has to be issued to LBA between cluster_size and 2*cluster_size. Causing allocation of second cluster in blobstore and assiging it LBA equal to number of LBAs per cluster. To fix this, case 1) disallows to RLE zeroes. Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/475494 (master) (cherry picked from commit 0d1aa0252d) Change-Id: I136282407966310c882ca97c960e9a71c442c469 Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478351 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>		2019-12-23 08:04:56 +00:00
..
blob.c	blob: fix sequentially allocated clusters starting from 0	2019-12-23 08:04:56 +00:00
bs_dev_common.c	blobstore/ut: Add mechanism for power failure simulation in ut	2019-06-19 08:39:00 +00:00
bs_scheduler.c	thread: Rename spdk_thread_msg to spdk_msg_fn	2018-12-18 23:31:08 +00:00
Makefile	test: move blob library unit tests to test/unit	2017-06-21 18:57:35 -04:00