sapconf: tuned.utils.commands: Writing to file /sys/block/.../queue/scheduler error: [Errno 22] Invalid argument

This document (7024298) is provided subject to the disclaimer at the end of this document.


SUSE Linux Enterprise Server 12 Service Pack 2 (SLES 12 SP2)
SUSE Linux Enterprise Server 12 Service Pack 3 (SLES 12 SP3)
SUSE Linux Enterprise Server 12 Service Pack 4 (SLES 12 SP4)
SUSE Linux Enterprise Server 12 Service Pack 5 (SLES 12 SP5)
SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 15 Service Pack 1 (SLES 15 SP1)


The file /var/log/tuned/tuned.log contains a warning like:

ERROR    tuned.utils.commands: Writing to file /sys/block/sdb/queue/scheduler error: [Errno 22] Invalid argument


Change the default scheduler from 'noop' to 'none'.

It is possible that the actual multiqueue scheduler is already 'none'. In this case you can ignore the warning or change the default to 'none' to avoid it.          
At the moment the scheduler can only be set globally for all devices. If you have both multiqueue and non-multique devices you can set the scheduler per device (see below)

  1. Determine the current sapconf profile with 'tuned-adm active'.
    The profile must be either 'sap-hana', 'sap-netweaver', 'sap-ase' or 'sap-bobj' (SLES 12) or 'sapconf' (SLES 15) or sapconf is not involved!


    # tuned-adm active
    Current active profile: sap-netweaver

  2. Create a directory /etc/tuned/<acitve profile> and a file tuned.conf inside with the following content:



    If you already have a configuration, change the [disk] section accordingly.

    If you want to set the schedulers per device, use the following example for your configuration:

    # section for devices with none

    # section for devices with cfq

    # everything else shall use noop

  3. Restart tuned by running 'systemctl restart tuned.service'


Devices can either support non-multiqueue schedulers (like noop, deadline, cfq) or multiqueue schedulers (like none, mq-deadline, bfq, kyber).
At the moment sapconf's default is 'noop'. With the next version both 'noop' and 'none' will become default.

Additional Information


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:7024298
  • Creation Date: 29-Nov-2019
  • Modified Date:03-Mar-2020
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact:

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center