In the initial bug report, you can see that /etc/default/nfs-kernel-server has
RPCNFSDPRIORITY=-10
But I don't think that has the intended effect, because all the nfsd processes
have a priority of 0, not -10.
I tried a local path to implement ionice-ness.
Added to /etc/default/nfs-kernel-server
# Runtime IO priority of server (see ionice(1) and start-stop-daemon(8))
# Value is class[:priority]
# class values: real-time, best-effort (default), idle
# priority values: 0-7 (only for realtime and best-effort) (default: 4),
optional
# default RPCNFSDIOPRIORITY=best-effort:4
RPCNFSDIOPRIORITY="real-time:0"
And changed /etc/init.d/nfs-kernel-server to
start-stop-daemon --start --oknodo --quiet \
--nicelevel $RPCNFSDPRIORITY \
--iosched $RPCNFSDIOPRIORITY \
--exec $PREFIX/sbin/rpc.nfsd -- $RPCNFSDCOUNT
(i.e. added --iosched line)
but requesting the ionice-ness of the nfsd processes showed it wasn't applied
either.
I don't know (yet?) whether this is an issue with s-s-d or the init script.
Attachment:
signature.asc
Description: This is a digitally signed message part.