All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amon Ott <a.ott@m-privacy.de>
To: Sage Weil <sage@newdream.net>,
	ceph-devel@vger.kernel.org, ceph-users@ceph.com
Subject: Re: the state of cephfs in giant
Date: Tue, 14 Oct 2014 09:31:56 +0200	[thread overview]
Message-ID: <543CD16C.6060708@m-privacy.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1410131114130.10561@cobra.newdream.net>

Am 13.10.2014 20:16, schrieb Sage Weil:
> We've been doing a lot of work on CephFS over the past few months. This
> is an update on the current state of things as of Giant.
...
> * Either the kernel client (kernel 3.17 or later) or userspace (ceph-fuse
>   or libcephfs) clients are in good working order.

Thanks for all the work and specially for concentrating on CephFS! We
have been watching and testing for years by now and really hope to
change our Clusters to CephFS soon.

For kernel maintenance reasons, we only want to run longterm stable
kernels. And for performance reasons and because of severe known
problems we want to avoid Fuse. How good are our chances of a stable
system with the kernel client in the latest longterm kernel 3.14? Will
there be further bugfixes or feature backports?

Thanks again,

Amon Ott
-- 
Dr. Amon Ott
m-privacy GmbH           Tel: +49 30 24342334
Werner-Voß-Damm 62       Fax: +49 30 99296856
12101 Berlin             http://www.m-privacy.de

Amtsgericht Charlottenburg, HRB 84946

Geschäftsführer:
 Dipl.-Kfm. Holger Maczkowsky,
 Roman Maczkowsky

GnuPG-Key-ID: 0x2DD3A649

--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-10-14  7:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-13 18:16 the state of cephfs in giant Sage Weil
2014-10-13 18:20 ` Wido den Hollander
2014-10-13 18:26   ` Sage Weil
2014-10-13 19:03 ` [ceph-users] " Eric Eastman
2014-10-13 20:56   ` Sage Weil
2014-10-14  7:31 ` Amon Ott [this message]
2014-10-14 13:09   ` Sage Weil
2014-10-14 14:23   ` [ceph-users] " Sage Weil
2014-10-15  0:16     ` Alphe Salas
     [not found]       ` <543DBCE9.2080605-g2h0fw6BmCNmR6Xm/wNWPw@public.gmane.org>
2014-10-15  2:06         ` Sage Weil
     [not found]     ` <alpine.DEB.2.00.1410140718050.10462-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2014-10-15  6:43       ` Amon Ott
2014-10-15 12:11         ` [ceph-users] " Ric Wheeler
     [not found]           ` <543E645E.4080405-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-10-15 13:13             ` Amon Ott
2014-10-15 14:58               ` [ceph-users] " Sage Weil
     [not found]                 ` <alpine.DEB.2.00.1410150754560.10462-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2014-10-15 16:47                   ` Alphe Salas
     [not found] ` <alpine.DEB.2.00.1410131114130.10561-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2014-10-14  9:57   ` Thomas Lemarchand
2014-10-14 13:11     ` [ceph-users] " Sage Weil
2014-10-30 10:55   ` Florian Haas
2014-10-30 14:36     ` [ceph-users] " John Spray
     [not found]     ` <CAPUexz_+jD7RMNSZEgy3h6WqKS4PSMj1fbyRgLKxQWHvctviNA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-10-30 15:28       ` Sage Weil

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=543CD16C.6060708@m-privacy.de \
    --to=a.ott@m-privacy.de \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ceph-users@ceph.com \
    --cc=sage@newdream.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.