From: Dongmao Zhang <dmzhang@suse.com>
To: lvm-devel@redhat.com
Subject: LVM2 test script failed, is it a read_ahead bug?
Date: Tue, 27 Aug 2013 18:00:05 +0800 [thread overview]
Message-ID: <521C78A5.5000108@suse.com> (raw)
Dear mail-list,
I met this in running the test case for lvm:
sh shell/read-ahead.sh FAILED:
#COMM "read ahead is properly inherited from underlying PV"
blockdev --setra 768 "$dev1"
#read-ahead.sh:34+ blockdev --setra 768 @TESTDIR@/dev/mapper/@PREFIX at pv1
vgscan
#read-ahead.sh:35+ vgscan
Reading all physical volumes. This may take a while...
Found volume group "@PREFIX at vg" using metadata type lvm2
WARNING: This metadata update is NOT backed up
lvcreate -n $lv -L4m $vg "$dev1"
#read-ahead.sh:36+ lvcreate -n LV -L4m @PREFIX at vg
@TESTDIR@/dev/mapper/@PREFIX at pv1
WARNING: This metadata update is NOT backed up
WARNING: This metadata update is NOT backed up
Logical volume "LV" created
test $(blockdev --getra $DM_DEV_DIR/$vg/$lv) -eq 768
blockdev --getra $DM_DEV_DIR/$vg/$lv
##read-ahead.sh:37+ blockdev --getra @TESTDIR@/dev/@PREFIX at vg/LV
#read-ahead.sh:37+ test 1024 -eq 768
The read_ahead of underlying device was set to 768. After creating the
logical volume device, lvm found the auto read ahead was 1024 which is
bigger than 768. So lvm selected the bigger number(1024) to the
read_ahead of logical volume.
However I think we should use the minimal read_ahead in underlying
device and auto-detected kernel parameter. if so, this behavior could be
consistent with the test script.
I suggest use:
diff --git a/libdm/libdm-common.c b/libdm/libdm-common.c
index 9043352..b9000f9 100644
--- a/libdm/libdm-common.c
+++ b/libdm/libdm-common.c
@@ -1225,7 +1225,7 @@ static int _set_dev_node_read_ahead(const char
*dev_name,
if (!get_dev_node_read_ahead(dev_name, major, minor,
¤t_read_ahead))
return_0;
- if (current_read_ahead >= read_ahead) {
+ if (current_read_ahead <= read_ahead) {
log_debug_activation("%s: retaining kernel read
ahead of %" PRIu32
" (requested %" PRIu32 ")",
dev_name, current_read_ahead, read_ahead);
If I am wrong, please correct me:)
thank you
next reply other threads:[~2013-08-27 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 10:00 Dongmao Zhang [this message]
2013-08-27 10:42 ` LVM2 test script failed, is it a read_ahead bug? Zdenek Kabelac
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=521C78A5.5000108@suse.com \
--to=dmzhang@suse.com \
--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.