Your message dated Sat, 03 Jun 2023 01:16:08 +0200
with message-id <4903142.0VBMTVartN@bagend>
and subject line Re: nfs-kernel-server: Please support specifying ionice-ness
has caused the Debian Bug report #944661,
regarding nfs-kernel-server: Please support specifying ionice-ness
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
944661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944661
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nfs-kernel-server
Version: 1:1.3.4-2.5
Severity: wishlist
Once can already specify nice-ness through RPCNFSDPRIORITY which sets
the --nicelevel parameter of start-stop-daemon.
But I want to also specify the ionice-ness and start-stop-daemon already
supports that through the --iosched parameter.
It would be great if that was enacted through /etc/init.d/nfs-kernel-server
invocation and preferably set via /etc/default/nfs-kernel-server file.
-- Package-specific info:
-- rpcinfo --
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 57068 status
100024 1 tcp 36259 status
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100227 3 tcp 2049
100003 3 udp 2049 nfs
100227 3 udp 2049
100021 1 udp 55374 nlockmgr
100021 3 udp 55374 nlockmgr
100021 4 udp 55374 nlockmgr
100021 1 tcp 39865 nlockmgr
100021 3 tcp 39865 nlockmgr
100021 4 tcp 39865 nlockmgr
100005 1 udp 46446 mountd
100005 1 tcp 39125 mountd
100005 2 udp 51891 mountd
100005 2 tcp 52869 mountd
100005 3 udp 38839 mountd
100005 3 tcp 45117 mountd
-- /etc/default/nfs-kernel-server --
RPCNFSDCOUNT=8
RPCNFSDPRIORITY=-10
RPCMOUNTDOPTS="--manage-gids"
NEED_SVCGSSD=""
RPCSVCGSSDOPTS=""
-- /etc/exports --
/srv/backup/
192.168.1.0/24(rw,no_root_squash,no_subtree_check)
/srv/media/
192.168.1.0/24(ro,no_root_squash,no_subtree_check)
-- /proc/fs/nfs/exports --
# Version 1.1
# Path Client(Flags) # IPs
-- System Information:
Debian Release: 10.1
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-6-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
Versions of packages nfs-kernel-server depends on:
ii keyutils 1.6-6
ii libblkid1 2.33.1-0.1
ii libc6 2.28-10
ii libcap2 1:2.25-2
ii libsqlite3-0 3.27.2-3
ii libtirpc3 1.1.4-0.4
ii libwrap0 7.6.q-28
ii lsb-base 10.2019051400
ii netbase 5.6
ii nfs-common 1:1.3.4-2.5
ii ucf 3.0038+nmu1
nfs-kernel-server recommends no packages.
nfs-kernel-server suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, 13 Mar 2022 20:16:26 +0100 Ben Hutchings <[email protected]> wrote:
> I/O scheduling priority can already be set through systemd service
> configuration. I don't anticipate adding any new features to the
> Debian-specific init scripts.
This was for the (very) old nfs version and as it's unlikely someone else
would file a similar bug, there's no need to keep this one open.
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
