From: Christoph Hellwig <hch@infradead.org>
To: DENIEL Philippe <philippe.deniel@CEA.FR>
Cc: xfs@oss.sgi.com
Subject: Re: Question : Using libhandle from xfsprogs and xfs actions made "by handle"
Date: Thu, 6 May 2010 16:35:14 -0400 [thread overview]
Message-ID: <20100506203514.GA6854@infradead.org> (raw)
In-Reply-To: <4BE178B3.8030501@cea.fr>
On Wed, May 05, 2010 at 03:54:59PM +0200, DENIEL Philippe wrote:
> When looking at XFS, I saw there was "open_by_handle" and
> "path_to_handle" calls. This sounds very very good to me : this sounds
> like kind of bridge to build a handle-based API to address XFS. But so
> far, I am a bit stuck : for exporting XFS through my NFS server, I would
> need to do "by handle" everything that can be done through POSIX calls,
> open/read/write/close files, create files/directories/symlinks, erasing
> or moving files... and so on. I do not know if this is possible with the
> calls in libhandle.so. But if I had such handle based tools, I think I
> could make a nice NFS server on top of XFS (I did this kind of port for
> LUSTRE (which has a full handle based API) in my NFS server and I had
> really good performances). Can someone provide me with information about
> this ?
For some reason the handle code currently rejects special files
(block/char/fifo) in open_by_handle. I can't see any good reason for
that and plan to submit a patch to lift that restriction. Except
for that libhandle is exactly what you want - there's various tools
that use it for that kind of work, the most prominent is
xfsdump/xfsrestore.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-05-06 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 13:54 Question : Using libhandle from xfsprogs and xfs actions made "by handle" DENIEL Philippe
2010-05-06 20:35 ` Christoph Hellwig [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=20100506203514.GA6854@infradead.org \
--to=hch@infradead.org \
--cc=philippe.deniel@CEA.FR \
--cc=xfs@oss.sgi.com \
/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