import ceph quincy 17.2.4

[ceph.git] / ceph / doc / dev / delayed-delete.rst

diff --git a/ceph/doc/dev/delayed-delete.rst b/ceph/doc/dev/delayed-delete.rst
index bf5f65a460893fa09153081b4a51c9be45475d2e..31f3e6b9727fed0f66d55a256281155ab0f3d209 100644 (file)
--- a/ceph/doc/dev/delayed-delete.rst
+++ b/ceph/doc/dev/delayed-delete.rst
@@ -2,11 +2,12 @@
  CephFS delayed deletion
 =========================
 
-When you delete a file, the data is not immediately removed. Each
-object in the file needs to be removed independently, and sending
-``size_of_file / stripe_size * replication_count`` messages would slow
-the client down too much, and use a too much of the clients
-bandwidth. Additionally, snapshots may mean some objects should not be
-deleted.
+The deletion of a file does not immediately remove its data. Each of the file's
+underlying objects must be removed independently. If these objects were removed 
+immediately, the client would have to send ``size_of_file / stripe_size *
+replication_count`` messages. This would consume significant bandwith and would
+slow the client unacceptably. If snapshots exist, their existence can prevent
+the deletion of objects associated with them.
 
-Instead, the file is marked as deleted on the MDS, and deleted lazily.
+In these cases, such files are (1) marked as deleted on the MDS and (2) deleted
+lazily.