From: Jimmy Tang <jtang@tchpc.tcd.ie>
To: Gregory Farnum <greg@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: ceph-fuse mount options
Date: Sat, 8 Sep 2012 09:05:28 +0100 [thread overview]
Message-ID: <20120908080528.GA7184@tchpc.tcd.ie> (raw)
In-Reply-To: <CAPYLRzgc_-9nTE+-Y6rm9aiBBVeEMZTfBs-ycRw3cFV8tL2AHg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
On Fri, Sep 07, 2012 at 09:22:34AM -0700, Gregory Farnum wrote:
> On Fri, Sep 7, 2012 at 9:03 AM, Jimmy Tang <jtang@tchpc.tcd.ie> wrote:
> > Hi All,
> >
> > I know that cephfs has the option picking which pools to use, will ceph-fuse be gaining this feature at any point in the future? Or is this feature available but isn't documented?
>
> It's not available ? making it work would require implementing FUSE's
> ioctl system, which we will probably do at some point, but is yet to
> be prioritized or placed anywhere.
>
> However, ceph-fuse does of course respect settings put in place by the
> kernel client, so if you just want to do a one-time configuration then
> you can do it via the kernel on one machine and use ceph-fuse
> elsewhere...
Ok thanks, thats good to know that it's probably on the roadmap. I
don't forsee us using the fuse module much, it's really only for
testing on RHEL6 based systems as the kernel hasn't quite caught up.
Jimmy
--
Jimmy Tang
Trinity Centre for High Performance Computing,
Lloyd Building, Trinity College Dublin, Dublin 2, Ireland.
http://www.tchpc.tcd.ie/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2012-09-08 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 16:03 ceph-fuse mount options Jimmy Tang
2012-09-07 16:22 ` Gregory Farnum
2012-09-08 8:05 ` Jimmy Tang [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=20120908080528.GA7184@tchpc.tcd.ie \
--to=jtang@tchpc.tcd.ie \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@inktank.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 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.