From: "J. Bruce Fields" <bfields@fieldses.org>
To: Steve Dickson <steved@redhat.com>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/1] exportfs: Stop racing exportfs on clusters
Date: Wed, 7 Mar 2012 15:36:49 -0500 [thread overview]
Message-ID: <20120307203649.GA582@fieldses.org> (raw)
In-Reply-To: <1331150190-18401-1-git-send-email-steved@redhat.com>
On Wed, Mar 07, 2012 at 02:56:30PM -0500, Steve Dickson wrote:
> This problem can occur when multiple cluster services fail over
> at the same time, causing missing high-available exports.
> Having a lot of nfs-exports will trigger this issue easier.
Isn't the locking in support/export/xtab.c supposed to take care of
this?
I may be confused--I forget what all these files are for....
--b.
>
> Signed-off-by: Steve Dickson <steved@redhat.com>
> ---
> support/include/exportfs.h | 4 ++++
> utils/exportfs/exportfs.c | 24 ++++++++++++++++++++++++
> 2 files changed, 28 insertions(+), 0 deletions(-)
>
> diff --git a/support/include/exportfs.h b/support/include/exportfs.h
> index 01e87dd..99916e5 100644
> --- a/support/include/exportfs.h
> +++ b/support/include/exportfs.h
> @@ -32,6 +32,10 @@ enum {
> FSLOC_STUB
> };
>
> +#ifndef EXP_LOCKFILE
> +#define EXP_LOCKFILE "/var/lib/nfs/export-lock"
> +#endif
> +
> typedef struct mclient {
> struct mclient * m_next;
> char * m_hostname;
> diff --git a/utils/exportfs/exportfs.c b/utils/exportfs/exportfs.c
> index 7432a65..769d438 100644
> --- a/utils/exportfs/exportfs.c
> +++ b/utils/exportfs/exportfs.c
> @@ -16,6 +16,7 @@
> #include <sys/stat.h>
> #include <sys/vfs.h>
> #include <sys/stat.h>
> +#include <sys/file.h>
> #include <unistd.h>
> #include <stdbool.h>
> #include <stdlib.h>
> @@ -44,6 +45,23 @@ static void validate_export(nfs_export *exp);
> static int matchhostname(const char *hostname1, const char *hostname2);
> static void export_d_read(const char *dname);
>
> +static const char *lockfile = EXP_LOCKFILE;
> +static int _lockfd = -1;
> +
> +void
> +grab_lockfile()
> +{
> + _lockfd = open(lockfile, O_CREAT|O_RDWR, 0666);
> + if (_lockfd != -1)
> + lockf(_lockfd, F_LOCK, 0);
> +}
> +void
> +release_lockfile()
> +{
> + if (_lockfd != -1)
> + lockf(_lockfd, F_ULOCK, 0);
> +}
> +
> int
> main(int argc, char **argv)
> {
> @@ -129,6 +147,12 @@ main(int argc, char **argv)
> return 0;
> }
> }
> + /*
> + * Serialize things as best we can
> + */
> + grab_lockfile();
> + atexit(release_lockfile);
> +
> if (f_export && ! f_ignore) {
> export_read(_PATH_EXPORTS);
> export_d_read(_PATH_EXPORTS_D);
> --
> 1.7.7.6
>
> --
> 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
next prev parent reply other threads:[~2012-03-07 20:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 19:56 [PATCH 1/1] exportfs: Stop racing exportfs on clusters Steve Dickson
2012-03-07 20:07 ` Chuck Lever
2012-03-07 20:19 ` Steve Dickson
2012-03-07 20:36 ` J. Bruce Fields [this message]
2012-03-07 20:50 ` J. Bruce Fields
2012-03-07 20:52 ` Chuck Lever
2012-03-08 15:11 ` Steve Dickson
2012-03-08 18:53 ` J. Bruce Fields
2012-03-07 20:53 ` Steve Dickson
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=20120307203649.GA582@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
/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