From: Christoph Hellwig <hch@infradead.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: David Woodhouse <dwmw2@infradead.org>,
Artem.Bityutskiy@nokia.com, linux-fsdevel@vger.kernel.org
Subject: Re: NFS and non-blkdev-backed FS?
Date: Sat, 16 Aug 2008 14:11:58 -0400 [thread overview]
Message-ID: <20080816181158.GA5787@infradead.org> (raw)
In-Reply-To: <1218809892.7037.3.camel@localhost>
On Fri, Aug 15, 2008 at 10:18:12AM -0400, Trond Myklebust wrote:
> On Fri, 2008-08-15 at 14:59 +0100, David Woodhouse wrote:
> > On Fri, 2008-08-15 at 11:55 +0300, Artem Bityutskiy wrote:
> > > UBIFS (as e.g. XFS) has a 16-byte UUID in superblock which is
> > > supposed to uniquely identify the file-system. I'd like to use
> > > this UUID as NFS FSID instead, however, I failed to find how
> > > to do this. Any hints how could I do this?
> >
> > By adding a 'get_fsid()' method to the export_ops structure...
> >
>
> If the uuid can be found by libuuid, then it will automatically be used
> as the default identifier by rpc.mount (man 5 exports). There should be
> no need for a new export_ops method.
We'll need it anyway, for exports not starting at the root of the
volume, and we'll need a method to be called when exporting a filesystem
to reject it if the filehandle couldn't fit into the space available
for the given nfs protocol version.
next prev parent reply other threads:[~2008-08-16 18:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 8:55 NFS and non-blkdev-backed FS? Artem Bityutskiy
2008-08-15 12:34 ` Christoph Hellwig
2008-08-15 13:59 ` David Woodhouse
2008-08-15 14:18 ` Trond Myklebust
2008-08-16 18:11 ` Christoph Hellwig [this message]
2008-08-16 19:37 ` Trond Myklebust
2008-08-18 11:17 ` David Woodhouse
2008-08-18 12:17 ` [PATCH 1/3] Fix handling of explicit uuid David Woodhouse
[not found] ` <1219061850.3184.378.camel-ZP4jZrcIevRpWr+L1FloEB2eb7JE58TQ@public.gmane.org>
2008-08-28 15:38 ` Steve Dickson
2008-08-28 15:38 ` Steve Dickson
[not found] ` <1219058258.3184.358.camel-ZP4jZrcIevRpWr+L1FloEB2eb7JE58TQ@public.gmane.org>
2008-08-18 12:17 ` [PATCH 2/3] Explicit UUID handling doesn't require blkid; factor out get_uuid_blkdev() David Woodhouse
2008-08-18 12:17 ` David Woodhouse
[not found] ` <1219061859.3184.380.camel-ZP4jZrcIevRpWr+L1FloEB2eb7JE58TQ@public.gmane.org>
2008-08-28 15:38 ` Steve Dickson
2008-08-28 15:38 ` Steve Dickson
2008-08-18 12:17 ` [PATCH 3/3] Use fsid from statfs for UUID if blkid can't cope (or not used) David Woodhouse
2008-08-18 12:17 ` David Woodhouse
[not found] ` <1219061860.3184.382.camel-ZP4jZrcIevRpWr+L1FloEB2eb7JE58TQ@public.gmane.org>
2008-08-28 15:39 ` Steve Dickson
2008-08-28 15:39 ` Steve Dickson
2008-08-18 16:00 ` [PATCH 4/3] Stop exportfs warning about needing fsid, when we actually have one David Woodhouse
2008-08-18 16:00 ` David Woodhouse
2008-08-28 15:39 ` Steve Dickson
2008-08-18 16:52 ` NFS and non-blkdev-backed FS? Bryan Henderson
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=20080816181158.GA5787@infradead.org \
--to=hch@infradead.org \
--cc=Artem.Bityutskiy@nokia.com \
--cc=dwmw2@infradead.org \
--cc=linux-fsdevel@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.