From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: kevin.strasser@linux.intel.com
Cc: yocto@yoctoproject.org
Subject: Re: [meta-baryon][PATCH 1/1] nfs-utils: workaround for nfsd regression in the 3.4 kernel
Date: Wed, 10 Oct 2012 18:16:16 +0100 [thread overview]
Message-ID: <4130728.thkuSetpic@helios> (raw)
In-Reply-To: <41548.10.7.202.71.1349112347.squirrel@linux.intel.com>
On Monday 01 October 2012 10:25:47 kevin.strasser@linux.intel.com wrote:
> > Hi Kevin,
> >
> > On Friday 28 September 2012 12:44:06 Kevin Strasser wrote:
> >> The version of nfsd used in 3.4 kernels tries to upcall the
> >> new reboot-recovery daemon and gets stuck if it is not found.
> >> This causes client mounts to fail and prints the following
> >> error message during boot:
> >>
> >> "NFSD: starting 90-second grace period
> >> NFSD: Unable to end grace period: -110"
> >>
> >> If the directory "/var/lib/nfs/v4recovery" exists, nfsd will
> >> revert back to the old method.
> >>
> >> Signed-off-by: Kevin Strasser <kevin.strasser@linux.intel.com>
> >> ---
> >>
> >> .../nfs-utils/nfs-utils_1.2.3.bbappend | 8 ++++++++
> >> 1 file changed, 8 insertions(+)
> >> create mode 100644
> >>
> >> recipes-connectivity/nfs-utils/nfs-utils_1.2.3.bbappend
> >>
> >> diff --git a/recipes-connectivity/nfs-utils/nfs-utils_1.2.3.bbappend
> >> b/recipes-connectivity/nfs-utils/nfs-utils_1.2.3.bbappend new file mode
> >> 100644
> >> index 0000000..2c91a93
> >> --- /dev/null
> >> +++ b/recipes-connectivity/nfs-utils/nfs-utils_1.2.3.bbappend
> >> @@ -0,0 +1,8 @@
> >> +PR = "r5"
> >
> > This needs to be:
> >
> > PRINC = "1"
> >
> > or, to ensure other layers can also increment the value:
> >
> > PRINC := "${@int(PRINC) + 1}"
>
> OK, that makes sense. I've made the changes and pushed them again to:
>
> git://git.yoctoproject.org/poky-contrib strassek/baryon-nfsd-regression
>
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=strassek/baryon-nf
> sd-regression
Merged to meta-baryon master, thanks.
> While we are on the subject, do you think this is something that should be
> added to poky?
Quite possibly. Would you mind opening up a bug for the issue?
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2012-10-10 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 19:43 [meta-baryon][PATCH 0/1] nfs regression workaround Kevin Strasser
2012-09-28 19:44 ` [meta-baryon][PATCH 1/1] nfs-utils: workaround for nfsd regression in the 3.4 kernel Kevin Strasser
2012-09-30 15:12 ` Paul Eggleton
2012-10-01 17:25 ` kevin.strasser
2012-10-10 17:16 ` Paul Eggleton [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=4130728.thkuSetpic@helios \
--to=paul.eggleton@linux.intel.com \
--cc=kevin.strasser@linux.intel.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.