From: Christoph Hellwig <hch@infradead.org>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Christoph Hellwig <hch@infradead.org>,
nfs@lists.sourceforge.net,
Pierre Ossman
<drzeus-list-p3sGCRWkH8CeZLLa646FqQ@public.gmane.org>
Subject: Re: [NFS] -EXDEV between mounts that are same fs
Date: Mon, 11 Feb 2008 23:54:04 -0500 [thread overview]
Message-ID: <20080212045404.GA625@infradead.org> (raw)
In-Reply-To: <20080211162136.GK25742@fieldses.org>
On Mon, Feb 11, 2008 at 11:21:36AM -0500, J. Bruce Fields wrote:
> > http://verein.lst.de/~hch/xfs/xfs-multiple-containers.txt
>
> Excellent, thanks, yes that's just what we'd want....
The proposal still lacks the idea of encoding the projid in the file
handle. But I think we could do that quite easily, but I'd do it after
my planned next round of the export interface cleanups, so that a
filehandle can see at mount time how much of the filehandle space it
has left and refuse the export if it doesn't fit (e.g. exporting with
various 64bit inode fields and NFSv2, or projids on NFSv2)
-------------------------------------------------------------------------
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-12 5:43 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
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 [this message]
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=20080212045404.GA625@infradead.org \
--to=hch@infradead.org \
--cc=bfields@fieldses.org \
--cc=drzeus-list-p3sGCRWkH8CeZLLa646FqQ@public.gmane.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 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.