From: NeilBrown <neilb@suse.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Question about nfsdcltrack --storagedir
Date: Wed, 09 Nov 2016 14:46:25 +1100 [thread overview]
Message-ID: <87k2cdmi26.fsf@notabene.neil.brown.name> (raw)
[-- Attachment #1: Type: text/plain, Size: 725 bytes --]
Hi,
I notice that nfsdcltrack has a "--storagedir" option.
I wonder how this can be used, given the nfsdcltrack is only(?) called
from the kernel and there is no(?) mechanism to pass extra options.
In a clustered-server context it would make sense(?) to share the
database between cluster nodes and it is easiest to do this if the
file in a separate filesystem (mounted as part of fail-over) rather
than in /var.
This can(?) be achieved using a symlink, but rpm likes to remove
symlinks to non-existent locations.
With NFSv3 the equivalent is the state files maintained by statd, and
these can be relocated by passing the -P option to rpc.statd.
How does one do a similar thing for NFSv4???
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]
next reply other threads:[~2016-11-09 3:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 3:46 NeilBrown [this message]
2016-11-09 11:57 ` Question about nfsdcltrack --storagedir Jeff Layton
2016-11-09 23:54 ` NeilBrown
2016-11-10 0:55 ` Jeff Layton
2016-11-10 4:58 ` [PATCH/RFC nfs-utils] nfsdcltrack: read configuration from a file NeilBrown
2016-11-10 15:00 ` Jeff Layton
2016-11-10 22:17 ` NeilBrown
2016-11-13 12:40 ` Jeff Layton
2016-11-15 16:52 ` Steve Dickson
2016-11-15 17:07 ` Steve Dickson
2016-11-16 18:22 ` Steve Dickson
2016-11-10 14:55 ` Question about nfsdcltrack --storagedir Chuck Lever
2016-11-10 22:32 ` NeilBrown
2016-11-11 16:19 ` Chuck Lever
2016-11-16 4:00 ` NeilBrown
2016-11-10 16:35 ` J. Bruce Fields
2016-11-10 22:35 ` NeilBrown
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=87k2cdmi26.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=jlayton@redhat.com \
--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).