From 30b84724d59256dbd56b02e8d0123529f801f5c1 Mon Sep 17 00:00:00 2001
From: Simon Rettberg
Date: Wed, 30 Sep 2020 11:38:14 +0200
Subject: [slx-dmsetup] Block zeroing not required in our use case

This is more useful if you pass volumes from the thin pool to
potentially untrused VMs or containers. We just run a normal file system
on top which takes care of zeroing for us already.
---
 modules.d/slx-dmsetup/scripts/dmsetup-slx-device | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/modules.d/slx-dmsetup/scripts/dmsetup-slx-device b/modules.d/slx-dmsetup/scripts/dmsetup-slx-device
index fd9a7175..f986f6e9 100755
--- a/modules.d/slx-dmsetup/scripts/dmsetup-slx-device
+++ b/modules.d/slx-dmsetup/scripts/dmsetup-slx-device
@@ -415,7 +415,7 @@ create_pool() {
 	# Convert MB to blocks
 	low_water_mark=$(( wanted_low_mb * 2048 / data_block_size ))
 	if ! dmsetup_create_noudevsync "${pool_dev##*/}" \
-		"0 $writable_device_size thin-pool $metadata_dev $pool_data_dev $data_block_size $low_water_mark"; then
+		"0 $writable_device_size thin-pool $metadata_dev $pool_data_dev $data_block_size $low_water_mark 1 skip_block_zeroing"; then
 		echo "$0: Failed to create thin-pool device on '$writable_device'."
 		return 1
 	fi
-- 
cgit v1.2.3-55-g7522