From 6a643ed82bf4f1660189fc29ea59facfcf49d008 Mon Sep 17 00:00:00 2001 From: Kai Lueke Date: Wed, 3 Apr 2024 16:35:25 +0900 Subject: [PATCH] kola: Increase amount of disk corruption in verity test For a particular image build the filesystem seemed to be more resistant to the corruption test, be it due to the corruption hitting other structures or some non-flushable cache covering more of the corrupted area. One can still trigger the verity panic by overwriting 100 MB instead of 10 MB. Increase the amount of zeros written by the corruption test. --- kola/tests/misc/verity.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kola/tests/misc/verity.go b/kola/tests/misc/verity.go index 5c29e4247..ad12439dc 100644 --- a/kola/tests/misc/verity.go +++ b/kola/tests/misc/verity.go @@ -96,8 +96,8 @@ func VerityCorruption(c cluster.TestCluster) { // get usr device, probably vda3 usrdev := util.GetUsrDeviceNode(c, m) - // write zero bytes to first 10 MB - c.MustSSH(m, fmt.Sprintf(`sudo dd if=/dev/zero of=%s bs=1M count=10 status=none`, usrdev)) + // write zero bytes to first 100 MB + c.MustSSH(m, fmt.Sprintf(`sudo dd if=/dev/zero of=%s bs=1M count=100 status=none`, usrdev)) // make sure we flush everything so the filesystem has to go through to the device backing verity before fetching a file from /usr // (done in one execution because after flushing command itself runs the corruption could already be detected,