From: Smart Weblications GmbH - Florian Wiessner <f.wiessner@smart-weblications.de>
To: Niko! <nicola.ranaldo@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Ceph fs stability
Date: Thu, 02 Aug 2012 19:26:49 +0200 [thread overview]
Message-ID: <501AB859.4040402@smart-weblications.de> (raw)
In-Reply-To: <501AB499.1080706@gmail.com>
Am 02.08.2012 19:10, schrieb Niko!:
> Hi!
>
> we are using ceph 0.48 on three nodes to provide rbd images for further four kvm
> nodes (not kernel mapped) with no big issues and would mount the ceph fs on the
> kvm nodes just to store xml virtual machine definitions in order to have them
> immediately in the case an host crashes (we are in multimds configuration). As
> ceph fs is not production ready what are the possible problems? May the fs
> corrupt the rbd pool or damages will be limited only to the data/metadata pools
> (acceptable for us)? may the fs hang the entire cluster or kvm client nodes?
>
Don't use it for now, it is too buggy - you sometimes cannot delete files or
rename them, or the fuse client crashes..
what we do instead is use a mapped rbd device with ocfs2 - works stable.
--
Mit freundlichen Grüßen,
Florian Wiessner
Smart Weblications GmbH
Martinsberger Str. 1
D-95119 Naila
fon.: +49 9282 9638 200
fax.: +49 9282 9638 205
24/7: +49 900 144 000 00 - 0,99 EUR/Min*
http://www.smart-weblications.de
--
Sitz der Gesellschaft: Naila
Geschäftsführer: Florian Wiessner
HRB-Nr.: HRB 3840 Amtsgericht Hof
*aus dem dt. Festnetz, ggf. abweichende Preise aus dem Mobilfunknetz
--
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
prev parent reply other threads:[~2012-08-02 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 17:10 Ceph fs stability Niko!
2012-08-02 17:24 ` Josh Durgin
2012-08-02 17:26 ` Smart Weblications GmbH - Florian Wiessner [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=501AB859.4040402@smart-weblications.de \
--to=f.wiessner@smart-weblications.de \
--cc=ceph-devel@vger.kernel.org \
--cc=nicola.ranaldo@gmail.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.