From: "J. Bruce Fields" <bfields@fieldses.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: nfs@lists.sourceforge.net,
Pierre Ossman
<drzeus-list-p3sGCRWkH8CeZLLa646FqQ@public.gmane.org>
Subject: Re: [NFS] -EXDEV between mounts that are same fs
Date: Sun, 10 Feb 2008 10:57:33 -0500 [thread overview]
Message-ID: <20080210155733.GC25571@fieldses.org> (raw)
In-Reply-To: <20080210153340.GB14540@infradead.org>
On Sun, Feb 10, 2008 at 10:33:40AM -0500, Christoph Hellwig wrote:
> On Sun, Feb 10, 2008 at 10:26:18AM -0500, J. Bruce Fields wrote:
> > > The point of the setup is of course to avoid exposing more information
> > > than is necessary, while still having the benefit of having a single
> > > pool of disk space for all exported resources.
> >
> > I notice that btrfs claims support for "subvolumes"--multiple filesystem
> > namespaces sharing the same storage. Seems like a useful feature for
> > this situation. I don't know whether it'd be possible to add to other
> > filesystems.
>
> That stuff is done using a code sniplet from me, which does nothing but
> allowing to mount into a subdirectory of a filesystem. It will look
> exactly the same as bind mounts.
To get the equivalent of subtree checking, we also need a reference from
each inode back to the subvolume it belongs to, so we can determine the
subvolume from a filehandle. I assume that's a more intrusive change.
--b.
> I have hacked up implementations for
> ext2 and xfs aswell and in the form btfs does it currently it would
> be doable for any filesystem. But to actually make it useful you'd
> need quotas for each subvolume which is something currently only
> xfs could provide (if I could be arsed into finally implementing
> my multiple subvolumes proposal fully).
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
next prev parent reply other threads:[~2008-02-10 15:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 19:05 [NFS] -EXDEV between mounts that are same fs Pierre Ossman
[not found] ` <20080209200503.6a11e88b-mgABNEgzgxm+PRNnhPf8W5YgPPQkE1Si@public.gmane.org>
2008-02-09 19:10 ` J. Bruce Fields
2008-02-09 20:35 ` Pierre Ossman
[not found] ` <20080209213511.59ff4e2c-mgABNEgzgxm+PRNnhPf8W5YgPPQkE1Si@public.gmane.org>
2008-02-09 20:40 ` Trond Myklebust
[not found] ` <1202589611.11035.0.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-02-09 20:57 ` Pierre Ossman
2008-02-09 23:14 ` J. Bruce Fields
2008-02-10 12:12 ` Pierre Ossman
[not found] ` <20080210131224.1d4ae39f-mgABNEgzgxm+PRNnhPf8W5YgPPQkE1Si@public.gmane.org>
2008-02-10 15:26 ` J. Bruce Fields
2008-02-10 15:33 ` Christoph Hellwig
2008-02-10 15:57 ` J. Bruce Fields [this message]
2008-02-10 15:59 ` Christoph Hellwig
2008-02-10 18:10 ` J. Bruce Fields
2008-02-10 18:21 ` Christoph Hellwig
2008-02-11 16:21 ` J. Bruce Fields
2008-02-12 4:54 ` Christoph Hellwig
2008-02-09 20:03 ` Trond Myklebust
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=20080210155733.GC25571@fieldses.org \
--to=bfields@fieldses.org \
--cc=drzeus-list-p3sGCRWkH8CeZLLa646FqQ@public.gmane.org \
--cc=hch@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox