Skip to main content

Ceph Reef (v18)

This document lists known critical bugs affecting Ceph Reef (v18) releases.

BlueStore Potential Corruption​

Severity: Critical
Affected Versions: 18.2.5, 18.2.6
Bug Report: https://tracker.ceph.com/issues/69764

Description​

Some versions of Ceph were released with a bug that may cause OSDs to crash and corrupt the on-disk data.

Recommendation​

Upgrade to a fixed version (17.2.9 or 18.2.7) as soon as possible.

RadosGW --bypass-gc Data Loss Bug​

Severity: Critical
Affected Versions: 18.2.[0-7] Bug Report: https://tracker.ceph.com/issues/73348

Description​

A long-standing data loss bug with --bypass-gc causes deletion of copied object data. If any of the deleted objects had been copied to/from other buckets, --bypass-gc deletes the data of those copies too. As a result, the copies are still visible to ListObjects requests but GetObject requests fail with NoSuchKey.

Note: This bug also affects Ceph Quincy (v17) and Squid (v19). See the Quincy known bugs and Squid known bugs pages for details.

Recommendation​

  • Use radosgw-admin bucket rm without --bypass-gc which correctly handles copied objects
  • Fixed in 18.2.8
  • If you've used --bypass-gc in the past, audit your buckets for objects with missing data

Stretch Mode PGs Inactive with Device-Class CRUSH Rules​

Severity: High Affected Versions: all releases up to and including 18.2.8 Bug Report: https://tracker.ceph.com/issues/81216

Description​

In stretch mode, pools whose CRUSH rule uses a device class (step take <site> class <class>) go inactive when a site or the inter-site link is lost, and stay inactive after it returns. Pools on rules without a device class are unaffected. The cluster reports HEALTH_OK until a site is lost.

Note: This bug also affects Squid (v19) and Tentacle (v20), and every earlier release with stretch mode.

Recommendation​