From: Anton <anton.vazir@gmail.com>
To: ceph-devel@lists.sourceforge.net
Cc: Sage Weil <sage@newdream.net>, ceph-devel@lists.sf.net
Subject: Re: v0.19.1 stable updates
Date: Tue, 9 Mar 2010 16:48:36 +0500 [thread overview]
Message-ID: <201003091648.36832.anton.vazir@gmail.com> (raw)
Sage, do you think CEPH now is ok (stable enough) to be
atleast sure that uploaded data will not be corrupted, (and
could be recovered in the case of fault) - for use as simple
file store - say in the scenario of "upload/modify rarely,
read often"?. Right now I use Gluster as clustered FS - but
overhead of 1+1 replication in Gluster is just HUGE
Regards,
Anton.
On Wednesday 03 March 2010, Sage Weil wrote:
> Hi all,
>
> We've pushed out some stable updates to master granches
> of the git trees and tagged a 0.19.1 stable release.
> For the server side, the fixes are minor: mainly a
> problem with /etc/init.d/ceph when /bin/sh is dash
> (ubuntu) and a rare mds crash. The kernel client fixes
> are a bit more significant: mainly a bad write(2) return
> value and a crash when snapshots were deleted.
>
> sage
>
> -- server side ------------------
>
> Sage Weil (8):
> debian: mount.ceph in /sbin, not /usr/sbin
> Makefile: include debian/
> Makefile: fix /sbin hack
> mds: fix sessionmap decoding
> init-ceph: don't barf on dash when no command
> cauthtool: --caps fn alone is a command
> debian: new release, push, build, publish scripts
> 0.19.1
>
> Yehuda Sadeh (1):
> automake: fix mount sbin dir when configured with
> prefix
>
>
> -- kernel client -----------------
>
> Alexander Beregalov (1):
> ceph: move dereference after NULL test
>
> Sage Weil (5):
> ceph: fix handle_forward parsing
> ceph: reset front len on return to msgpool; BUG on
> mismatched front iov ceph: set osd request message front
> length correctly ceph: fix osdmap decoding when pools
> include (removed) snaps ceph: v0.19.1 stable release
>
> Yehuda Sadeh (1):
> ceph: don't clobber write return value when using
> O_SYNC
>
>
> ---------------------------------------------------------
> --------------------- Download Intel® Parallel
> Studio Eval
> Try the new software tools for yourself. Speed compiling,
> find bugs proactively, and fine-tune applications for
> parallel performance. See why Intel Parallel Studio got
> high marks during beta. http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Ceph-devel mailing list
> Ceph-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ceph-devel
>
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
next reply other threads:[~2010-03-09 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 11:48 Anton [this message]
2010-03-09 13:29 ` v0.19.1 stable updates Roland Rabben
2010-03-10 13:33 ` Anton
2010-03-10 16:43 ` Sage Weil
-- strict thread matches above, loose matches on Subject: below --
2010-03-02 19:19 Sage Weil
2010-03-09 11:26 ` Anton
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=201003091648.36832.anton.vazir@gmail.com \
--to=anton.vazir@gmail.com \
--cc=ceph-devel@lists.sf.net \
--cc=ceph-devel@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox