require consistency to be enforced by the storage system. Writes will
be forwarded to the base tier, but objects that are read will get
promoted to the cache. No attempt is made by Ceph to ensure that the
-contents of the cache tier(s) are consistent in the presense of object
+contents of the cache tier(s) are consistent in the presence of object
updates.
Cache sizing
1. Either there is no DeletingStateRef for the pg, or it failed to cancel
2. We succeeded in canceling the deletion.
-In case 1., we proceed as if there were no deletion occuring, except that
+In case 1., we proceed as if there were no deletion occurring, except that
we avoid writing to the PG until the deletion finishes. In case 2., we
proceed as in case 1., except that we first mark the PG as backfilling.
If the *head* is deleted while there are still clones, a *snapdir* object
is created instead to house the *SnapSet*.
-Addionally, the *object_info_t* on each clone includes a vector of snaps
+Additionally, the *object_info_t* on each clone includes a vector of snaps
for which clone is defined.
Snap Removal
forced writeback of small writes too eagerly killing performance.
WBThrottle tracks unflushed io per hobject_t and ::fsyncs in lru
-order once the start_flusher threshhold is exceeded for any of
+order once the start_flusher threshold is exceeded for any of
dirty bytes, dirty ios, or dirty inodes. While any of these exceed
the hard_limit, we block on throttle() in _do_op.
Next add any addition debian packages that are needed such as leveldb and
ceph-deploy. See the Debian Backports section below.
-Debian packages are signed when added to the repo, so no furthur action is
+Debian packages are signed when added to the repo, so no further action is
needed.