My Favorites

Close

Please to see your favorites.

  • Bookmark
  • Email Document
  • Printer Friendly
  • Favorite
  • Rating:

saptune: WARNING saptune.io.go:66: 'noop' is not a valid scheduler for device

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

Environment

SUSE Linux Enterprise Server for SAP Applications 12 Service Pack 2
SUSE Linux Enterprise Server for SAP Applications 12 Service Pack 3
SUSE Linux Enterprise Server for SAP Applications 12 Service Pack 4
SUSE Linux Enterprise Server for SAP Applications 12 Service Pack 5
SUSE Linux Enterprise Server for SAP Applications 15
SUSE Linux Enterprise Server for SAP Applications 15 Service Pack 1

Situation

The file /var/log/tuned/tuned.log or the output of a saptune command contains a warning like:

WARNING  saptune.io.go:66: 'none' is not a valid scheduler for device 'sda', skipping.

Resolution

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 tell saptune to ignore the scheduler (see below) and set them with other tools.
          
  1. Run 'saptune note verify' to identify the SAP Note which sets the scheduler (IO_SCHEDULER).

    Example:

    # saptune note verify
    ...
       SAPNote, Version | Parameter                          | Expected                  | Override  | Actual                    | Compliant
    --------------------+------------------------------------+---------------------------+-----------+---------------------------+-----------
    ...
       1984787, 32      | IO_SCHEDULER_sda                   | noop                      |           | mq-deadline               | no
       1984787, 32      | IO_SCHEDULER_sdb                   | noop                      |           | mq-deadline               | no
       1984787, 32      | IO_SCHEDULER_sr0                   | noop                      |           | mq-deadline               | no
    ...

  2. Create an override file with 'saptune note customise <Note ID>' which opens an editor (vim) with a copy of the entire SAP Note configuration.
    Remove everything except the lines in the example here and save the changes.

    Example:

    # saptune note customise 1984787

    [block]
    IO_SCHEDULER=none


    If you want saptune to ignore the scheduler settings please use the following content:

    [block]
    IO_SCHEDULER=

    As an alternative you can create a file /etc/saptune/override/<Note ID> with this content.

  3. Re-apply the changes by running 'saptune daemon start'

Cause

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

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/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:7024299
  • Creation Date:29-NOV-19
  • Modified Date:29-NOV-19
    • NovellSUSE Linux Enterprise Server for SAP Applications
< Back to Support Search

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