From: Adam Carter <adamcarter3@gmail.com>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] nfsv4 issues
Date: Sun, 24 Jul 2016 17:37:56 +1000 [thread overview]
Message-ID: <CAC=wYCFbknRCx_a7xup+=Y9eV=g71L-5b_JhKikTEDzvPLxD0A@mail.gmail.com> (raw)
In-Reply-To: <CAC=wYCFzb=Sh_=vQ=psONpdtHBX3qi4OT_CUzq8jye9_TJy93w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 398 bytes --]
I've added the directory, and after restarting syslog now has new entries;
> kernel: [912267.948883] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4
> state recovery directory
> kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery
> directory
>
> I will test shortly and report back - thanks!
>
Confirmed - this fixes the 30 second delay. Should i log a bug for these
issues?
[-- Attachment #2: Type: text/html, Size: 719 bytes --]
next prev parent reply other threads:[~2016-07-24 7:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 4:49 [gentoo-user] nfsv4 issues Adam Carter
2016-07-19 23:34 ` Tom H
2016-07-21 2:51 ` Adam Carter
2016-07-22 12:46 ` Tom H
2016-07-23 0:22 ` Adam Carter
2016-07-24 7:37 ` Adam Carter [this message]
2016-07-24 16:47 ` Tom H
2016-07-24 16:21 ` Tom H
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='CAC=wYCFbknRCx_a7xup+=Y9eV=g71L-5b_JhKikTEDzvPLxD0A@mail.gmail.com' \
--to=adamcarter3@gmail.com \
--cc=gentoo-user@lists.gentoo.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