From: James Pearson <jcpearson@gmail.com>
To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re-exporting NFS shares with a generated fsid as a UUID?
Date: Tue, 22 Jul 2025 09:49:38 +0100 [thread overview]
Message-ID: <054308ba-bad7-4e61-a11d-34f041399543@gmail.com> (raw)
I've been experimenting with re-exporting NFS shares and using the
external fsidd service via the 'reexport' option - which all seems to
work OK
As it is possible to use a UUID as a fsid for an export, would it
possible to allow an automatically generated fsid as a UUID - i.e.
instead of talking to an external service to provide a fsid, just
generate a UUID which would be a hash (of some kind) of the exported
path ? i.e. no need to use an external database to supply a consistent
fsid ?
Thanks
James Pearson
next reply other threads:[~2025-07-22 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 8:49 James Pearson [this message]
2025-07-22 11:36 ` Re-exporting NFS shares with a generated fsid as a UUID? Daire Byrne
2025-07-22 14:57 ` James Pearson
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=054308ba-bad7-4e61-a11d-34f041399543@gmail.com \
--to=jcpearson@gmail.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