From: Abhishek Lekshmanan <abhishek@suse.com>
To: ceph-announce@ceph.io, ceph-users@ceph.io, dev@ceph.io,
ceph-devel@vger.kernel.org, ceph-maintainers@ceph.io
Subject: v15.2.5 octopus released
Date: Wed, 16 Sep 2020 17:10:11 +0200 [thread overview]
Message-ID: <87een1g3l8.fsf@suse.com> (raw)
This is the fifth backport release of the Ceph Octopus stable release
series. This release brings a range of fixes across all components. We
recommend that all Octopus users upgrade to this release.
Notable Changes
---------------
* CephFS: Automatic static subtree partitioning policies may now be configured
using the new distributed and random ephemeral pinning extended attributes on
directories. See the documentation for more information:
https://docs.ceph.com/docs/master/cephfs/multimds/
* Monitors now have a config option `mon_osd_warn_num_repaired`, 10 by default.
If any OSD has repaired more than this many I/O errors in stored data a
`OSD_TOO_MANY_REPAIRS` health warning is generated.
* Now when noscrub and/or no deep-scrub flags are set globally or per pool,
scheduled scrubs of the type disabled will be aborted. All user initiated
scrubs are NOT interrupted.
* Fix an issue with osdmaps not being trimmed in a healthy cluster (
issue#47297, pr#36981)
For the detailed changelog please refer to the blog entry at
https://ceph.io/releases/v15-2-5-octopus-released/
Getting Ceph
------------
* Git at git://github.com/ceph/ceph.git
* Tarball at http://download.ceph.com/tarballs/ceph-15.2.5.tar.gz
* For packages, see http://docs.ceph.com/docs/master/install/get-packages/
* Release git sha1: 2c93eff00150f0cc5f106a559557a58d3d7b6f1f
--
Abhishek Lekshmanan
SUSE Software Solutions Germany GmbH
GF: Felix Imendörffer, HRB 36809 (AG Nürnberg)
reply other threads:[~2020-09-16 17:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87een1g3l8.fsf@suse.com \
--to=abhishek@suse.com \
--cc=ceph-announce@ceph.io \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-maintainers@ceph.io \
--cc=ceph-users@ceph.io \
--cc=dev@ceph.io \
/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