From: Zdenek Kabelac <zkabelac@sourceware.org>
To: lvm-devel@redhat.com
Subject: main - tests: enforce 4K block for integrity fs
Date: Sun, 23 Apr 2023 11:09:34 +0000 (GMT) [thread overview]
Message-ID: <20230423110934.C9B453858C66@sourceware.org> (raw)
Gitweb: https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=ce8835d4c429bd87da5731e3015d9ddc9e3fb888
Commit: ce8835d4c429bd87da5731e3015d9ddc9e3fb888
Parent: 7cf5feb7d245d22d4968b95f3b7cfb6467461ff2
Author: Zdenek Kabelac <zkabelac@redhat.com>
AuthorDate: Sun Apr 23 00:03:43 2023 +0200
Committer: Zdenek Kabelac <zkabelac@redhat.com>
CommitterDate: Sun Apr 23 00:03:43 2023 +0200
tests: enforce 4K block for integrity fs
With raid tests it's important we don't get spread of 4K file
across 1K block on a multiple disk stripe - so use 4K block size
for ext4 fs.
---
test/shell/integrity-caching.sh | 4 ++--
test/shell/integrity.sh | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/test/shell/integrity-caching.sh b/test/shell/integrity-caching.sh
index 52aec98ce..73d33de18 100644
--- a/test/shell/integrity-caching.sh
+++ b/test/shell/integrity-caching.sh
@@ -45,7 +45,7 @@ _prepare_vg() {
}
_test_fs_with_read_repair() {
- mkfs.ext4 "$DM_DEV_DIR/$vg/$lv1"
+ mkfs.ext4 -b 4096 "$DM_DEV_DIR/$vg/$lv1"
mount "$DM_DEV_DIR/$vg/$lv1" $mnt
@@ -92,7 +92,7 @@ _test_fs_with_read_repair() {
}
_add_new_data_to_mnt() {
- mkfs.ext4 "$DM_DEV_DIR/$vg/$lv1"
+ mkfs.ext4 -b 4096 "$DM_DEV_DIR/$vg/$lv1"
mount "$DM_DEV_DIR/$vg/$lv1" $mnt
diff --git a/test/shell/integrity.sh b/test/shell/integrity.sh
index c649bef11..b55855ab4 100644
--- a/test/shell/integrity.sh
+++ b/test/shell/integrity.sh
@@ -45,7 +45,7 @@ _prepare_vg() {
}
_test_fs_with_read_repair() {
- mkfs.ext4 "$DM_DEV_DIR/$vg/$lv1"
+ mkfs.ext4 -b 4096 "$DM_DEV_DIR/$vg/$lv1"
mount "$DM_DEV_DIR/$vg/$lv1" $mnt
@@ -73,7 +73,7 @@ _test_fs_with_read_repair() {
}
_add_new_data_to_mnt() {
- mkfs.ext4 "$DM_DEV_DIR/$vg/$lv1"
+ mkfs.ext4 -b 4096 "$DM_DEV_DIR/$vg/$lv1"
mount "$DM_DEV_DIR/$vg/$lv1" $mnt
reply other threads:[~2023-04-23 11:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230423110934.C9B453858C66@sourceware.org \
--to=zkabelac@sourceware.org \
--cc=lvm-devel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.