I/O Scheduler changes for NVMe devices after patching
This document (000019772) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise Server 15
Situation
For example, a server before being patched shows the scheduler set as none:
lsblk -o NAME,FSTYPE,ROTA,SCHED NAME FSTYPE ROTA SCHED nvme0n1 0 none └─nvme0n1p1 xfs 0 noneAfter patching and rebooting, the scheduler has changed to mq-deadline:
lsblk -o NAME,FSTYPE,ROTA,SCHED NAME FSTYPE ROTA SCHED nvme0n1 0 mq-deadline └─nvme0n1p1 xfs 0 mq-deadline
Resolution
echo SCHEDULER > /sys/block/DEVICE/queue/scheduler
For example, to change from mq-deadline back to none, run the following command:
echo none > /sys/block/nvme0n1/queue/scheduler
To make these changes persistent after reboot, edit the file, /usr/lib/udev/rules.d/60-io-scheduler.rules and remove the following lines:
# MQ: deadline scheduler for SSD ENV{.IS_MQ}=="1", ATTR{queue/rotational}=="0", ATTR{queue/scheduler}="mq-deadline"
Cause
Additional Information
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000019772
- Creation Date: 02-Nov-2020
- Modified Date:14-May-2024
-
- SUSE Linux Enterprise Server
- SUSE Linux Enterprise Server for SAP Applications
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com