From: Frank van Maarseveen <frankvm@frankvm.com>
To: Linux NFS mailing list <nfs@lists.sourceforge.net>
Subject: exportfs bug
Date: Wed, 16 May 2007 17:34:38 +0200 [thread overview]
Message-ID: <20070516153438.GA30140@janus> (raw)
Multiple exportfs commands within a second don't work as expected. This
is caused by writing either the wall clock time or the /etc/exports mtime
to various /proc files, all with the granularity of 1 second. Scripts
can easily issue more than one exportfs command within that time.
A repeated sequence of
- script modifies /etc/exports
- script runs exportfs -r
fails horribly (client gets EACCES, ESTALE)
IMO exportfs should at least hide the time granularity problem e.g. by
maintaining a timestamp file, waiting if necessary.
--
Frank
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2007-05-16 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 15:34 Frank van Maarseveen [this message]
2007-05-16 16:13 ` exportfs bug J. Bruce Fields
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=20070516153438.GA30140@janus \
--to=frankvm@frankvm.com \
--cc=nfs@lists.sourceforge.net \
/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.