From: Neil Brown <neilb@suse.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-btrfs@vger.kernel.org, linux-nfs@vger.kernel.org, jeffm@suse.com
Subject: Re: NFS exporting btrfs subvolumes.
Date: Wed, 2 Jun 2010 15:03:51 +1000 [thread overview]
Message-ID: <20100602150351.592e36a8@notabene.brown> (raw)
In-Reply-To: <1275450980.4509.13.camel@heimdal.trondhjem.org>
On Tue, 01 Jun 2010 23:56:20 -0400
Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
> On Wed, 2010-06-02 at 13:41 +1000, Neil Brown wrote:
> > NFS needs a unique identifier for a filesystem to be able to export it.
> <snip>
> > Can anyone suggest a better way to get a good uuid for a btrfs filesystem?
>
> How about just adding the btrfs subvolid to the filehandle and using
> that to remove the ambiguity?
The filehandle has two parts - one part identifies the filesystem
(i.e. vfsmnt), the other identifies the file (the dentry).
We would need to get the btrfs subvolid into the filesystem part,
and that is set (and looked-up) by mountd in user-space.
I think you are suggesting getting the btrfs kernel module to put the
subvolid in the filehandle, but that would only go in the 'file' part
of the handle, so it would not be sufficient.
We need a user-space program - preferably without too much
filesystem-specific info - to be able to differentiate subvolumes.
Thanks,
NeilBrown
prev parent reply other threads:[~2010-06-02 5:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 3:41 NFS exporting btrfs subvolumes Neil Brown
2010-06-02 3:56 ` Trond Myklebust
2010-06-02 5:03 ` Neil Brown [this message]
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=20100602150351.592e36a8@notabene.brown \
--to=neilb@suse.de \
--cc=jeffm@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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.