10 Commits

Author	SHA1	Message	Date
Zdenek Kabelac	1bf1aca544	tests: integrity switch to ext4 ... Since we would need to create a lot of 300M filesystem, switch this test suite to ext4.	2022-09-21 14:58:34 +02:00
Zdenek Kabelac	94c4af232c	tests: prohibit 4K brd device with integrity ... Older kernels hit these errors: device-mapper: integrity: Bio not aligned on 8 sectors: 0x8ffc, 0x4	2021-03-20 10:52:24 +01:00
Zdenek Kabelac	531a475afc	tests: use 4K with mkfs.xfs ... If the test runs of loop device backend with 512 sectors, xfs selects this smaller sector size and then data do not fit (we would need -l9 with most of 'raids'). With 4K sectors data always fits.	2020-09-20 00:37:21 +02:00
Zdenek Kabelac	9fbcba1c40	tests: update integrity-dmeventd ... Use tee. Switch to more simple generator with awk (which doesn't produce long debug trace) Sync before sleep to provoke raid action.	2020-09-18 17:30:45 +02:00
Zdenek Kabelac	a4137412bf	tests: also use sed to shorten log output	2020-09-18 00:31:59 +02:00
Zdenek Kabelac	fe77d1a710	tests: avoid using string ... String 'TEST WARNING' may not be present in the test script itself. Add '\ ' to avoid 'grep' matching test as the test with warning.	2020-09-12 13:24:03 +02:00
Marian Csontos	be61bd6ff5	test: Warn and exit on problematic integrity device behavior ... The first leg of integrity enabled raid device sometimes does not get recalculated.	2020-05-28 17:04:35 +02:00
Marian Csontos	53803821de	test: Use printf to generate data ... ...to avoid unnecessary dependency on python	2020-05-21 15:33:24 +02:00
Marian Csontos	b5811b7c9c	tests: Use python single liner to generate data	2020-05-21 15:11:22 +02:00
David Teigland	d9e8895a96	Allow dm-integrity to be used for raid images ... dm-integrity stores checksums of the data written to an LV, and returns an error if data read from the LV does not match the previously saved checksum. When used on raid images, dm-raid will correct the error by reading the block from another image, and the device user sees no error. The integrity metadata (checksums) are stored on an internal LV allocated by lvm for each linear image. The internal LV is allocated on the same PV as the image. Create a raid LV with an integrity layer over each raid image (for raid levels 1,4,5,6,10): lvcreate --type raidN --raidintegrity y [options] Add an integrity layer to images of an existing raid LV: lvconvert --raidintegrity y LV Remove the integrity layer from images of a raid LV: lvconvert --raidintegrity n LV Settings Use --raidintegritymode journal|bitmap (journal is default) to configure the method used by dm-integrity to ensure crash consistency. Initialization When integrity is added to an LV, the kernel needs to initialize the integrity metadata/checksums for all blocks in the LV. The data corruption checking performed by dm-integrity will only operate on areas of the LV that are already initialized. The progress of integrity initialization is reported by the "syncpercent" LV reporting field (and under the Cpy%Sync lvs column.) Example: create a raid1 LV with integrity: $ lvcreate --type raid1 -m1 --raidintegrity y -n rr -L1G foo Creating integrity metadata LV rr_rimage_0_imeta with size 12.00 MiB. Logical volume "rr_rimage_0_imeta" created. Creating integrity metadata LV rr_rimage_1_imeta with size 12.00 MiB. Logical volume "rr_rimage_1_imeta" created. Logical volume "rr" created. $ lvs -a foo LV VG Attr LSize Origin Cpy%Sync rr foo rwi-a-r--- 1.00g 4.93 [rr_rimage_0] foo gwi-aor--- 1.00g [rr_rimage_0_iorig] 41.02 [rr_rimage_0_imeta] foo ewi-ao---- 12.00m [rr_rimage_0_iorig] foo -wi-ao---- 1.00g [rr_rimage_1] foo gwi-aor--- 1.00g [rr_rimage_1_iorig] 39.45 [rr_rimage_1_imeta] foo ewi-ao---- 12.00m [rr_rimage_1_iorig] foo -wi-ao---- 1.00g [rr_rmeta_0] foo ewi-aor--- 4.00m [rr_rmeta_1] foo ewi-aor--- 4.00m	2020-04-15 12:10:32 -05:00