Ceph

There's a fix here: https://github.com/ceph/ceph/pull/6918

Basically I've moved the check for a full pool to the right place (before updating the cached ObjectContext)
without changing the check itself (well, almost).

The commit introduces a regression and is reverted by http://tracker.ceph.com/issues/15019

The commit introduces a regression

The commit exposes a bug in the test which assumes it's possible to write more data than the storage capacity is.
I believe that OSD should reject such writes to prevent further damage (ENOSPC handling in filesystems' code is not 100% fool proof), and it does so in Infernalis and Jewel.

and is reverted by http://tracker.ceph.com/issues/15019

I don't think reverting it is a good idea, the test case itself should be fixed instead.
Even if we want to pretend that it's possible to write 144 MB of data to a 100 MB drive
the check should be slightly modified, that is, https://github.com/ceph/ceph/blob/hammer/src/osd/ReplicatedPG.cc#L5693 should be removed,
instead of reintroducing the obc corruption. However I think checking for a full OSD is actually correct.