From: Gionatan Danti <g.danti@assyoma.it>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Forcing a specific io scheduler
Date: Wed, 11 Sep 2019 00:58:20 +0200 [thread overview]
Message-ID: <c9570c19bfd78579f77ff85e81ce0137@assyoma.it> (raw)
Hi all,
I have a (virtual) block devices which does not expose any io scheduler:
[root@localhost block]# cat /sys/block/zd0/queue/scheduler
none
I created an lvm volume on top of that block devices with:
[root@localhost ~]# pvcreate /dev/zd0
Physical volume "/dev/zd0" successfully created.
[root@localhost ~]# vgcreate vg_test /dev/zd0
Volume group "vg_test" successfully created
[root@localhost ~]# lvcreate vg_test --name lv_test -l +100%FREE
Logical volume "lv_test" created.
With my surprise, I can not select any additional io scheduler:
[root@localhost block]# cat /sys/block/dm-2/queue/scheduler
none
I am missing something? Can a scheduler be forced on a lvm volume?
Thanks.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
reply other threads:[~2019-09-10 22:58 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=c9570c19bfd78579f77ff85e81ce0137@assyoma.it \
--to=g.danti@assyoma.it \
--cc=linux-lvm@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.