From: bfields@fieldses.org (J. Bruce Fields)
To: Daniel Pocock <daniel@pocock.pro>
Cc: linux-nfs@vger.kernel.org
Subject: Re: improving NFS stability in next Debian release
Date: Wed, 14 Dec 2016 14:28:16 -0500 [thread overview]
Message-ID: <20161214192816.GB2212@fieldses.org> (raw)
In-Reply-To: <4415ff5c-98c3-629d-aefd-a5e677688bbb@pocock.pro>
On Sun, Dec 11, 2016 at 08:01:12PM +0100, Daniel Pocock wrote:
> NFS was quite stable with previous Debian versions but in Jessie, the
> current stable release, it has been prone to crashes under load (kernel
> 3.16, bug report[1]). A user also asked[2] about this on the
> linux-fsdevel list a few months ago.
>
> With the next Debian release freeze approaching, what will it take to
> ensure a stable experience for NFS users?
>
> Are there any known problems for NFS in the current Debian kernel[3]?
>
> Which version of nfs-utils should be distributed? The current package
> is quite old[4].
>
> Debian jessie-backports contains a 4.7.9 kernel, should that be
> compatible with the nfs-utils package v1.2.8 and other related things in
> jessie?
We're pretty conservative about changes to the nfs-utils<->kernel
interfaces. I wouldn't expect incompatibilites between versions only a
few years out of sync.
As for questions about known problems and stability of particular kernel
versions, sorry, I really don't have a simple answer. I think it's
mainly a matter of investigating individual bug reports and keeping an
eye on upstream patches, especially anything marked for stable.
--b.
>
> Regards,
>
> Daniel
>
>
> 1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847549
> 2. http://www.spinics.net/lists/linux-fsdevel/msg98540.html
> 3. https://packages.qa.debian.org/l/linux.html
> 4. https://packages.qa.debian.org/n/nfs-utils.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-12-14 19:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 19:01 improving NFS stability in next Debian release Daniel Pocock
2016-12-14 19:27 ` Daniel Pocock
2016-12-14 22:47 ` Bug#847681: " Ben Hutchings
2016-12-14 19:28 ` J. Bruce Fields [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161214192816.GB2212@fieldses.org \
--to=bfields@fieldses.org \
--cc=daniel@pocock.pro \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).