From: Rich Dubielzig <rich.dubielzig@windriver.com>
To: <Openembedded-core@lists.openembedded.org>
Cc: rich.dubielzig@windriver.com
Subject: [PATCH] nfs-utils: Add scratch directory for NFS upcall state storage
Date: Mon, 25 Feb 2013 10:44:59 -0800 [thread overview]
Message-ID: <1361817899-22185-1-git-send-email-rich.dubielzig@windriver.com> (raw)
When the /var/lib/nfs/v4recovery directory is not present, NFSD cannot
record the upcall state and cannot end the 90-second grace period on
startup. This is true even when NFS4 is not being served according to
nfsstat.
More details and discussion here:
https://lkml.org/lkml/2012/6/11/206
Signed-off-by: Rich Dubielzig <rich.dubielzig@windriver.com>
---
.../nfs-utils/nfs-utils_1.2.3.bb | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/meta/recipes-connectivity/nfs-utils/nfs-utils_1.2.3.bb b/meta/recipes-connectivity/nfs-utils/nfs-utils_1.2.3.bb
index 84c4464..a0b2399 100644
--- a/meta/recipes-connectivity/nfs-utils/nfs-utils_1.2.3.bb
+++ b/meta/recipes-connectivity/nfs-utils/nfs-utils_1.2.3.bb
@@ -12,7 +12,7 @@ DEPENDS = "libcap libnfsidmap libevent util-linux tcp-wrappers"
RDEPENDS_${PN} = "rpcbind"
RRECOMMENDS_${PN} = "kernel-module-nfsd"
-PR = "r4"
+PR = "r5"
SRC_URI = "${SOURCEFORGE_MIRROR}/nfs/nfs-utils-${PV}.tar.bz2 \
file://nfs-utils-1.0.6-uclibc.patch \
@@ -58,4 +58,7 @@ do_install_append () {
rm -f ${D}${sbindir}/rpcdebug
rm -f ${D}${sbindir}/rpcgen
rm -f ${D}${sbindir}/locktest
+
+ # needed to allow NFSD to end its grace period
+ install -d ${D}/var/lib/nfs/v4recovery
}
--
1.7.1
next reply other threads:[~2013-02-25 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 18:44 Rich Dubielzig [this message]
2013-02-25 23:45 ` [PATCH] nfs-utils: Add scratch directory for NFS upcall state storage Saul Wold
2013-02-26 20:02 ` Dubielzig, Rich
2013-02-27 0:03 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2013-02-26 23:59 Rich Dubielzig
2013-02-25 18:33 Rich Dubielzig
2013-02-25 18:06 Rich Dubielzig
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=1361817899-22185-1-git-send-email-rich.dubielzig@windriver.com \
--to=rich.dubielzig@windriver.com \
--cc=Openembedded-core@lists.openembedded.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