os/filestore: blacklist same ENOENT failures as bluestore

FileStore doesn't care per se, but they indicate buggy calling code, and
we want to catch all bad callers!

Signed-off-by: Sage Weil <sage@redhat.com>

diff --git a/src/os/filestore/FileStore.cc b/src/os/filestore/FileStore.cc
index d3f632192b5b0bf8de19cf5affac1f71fd863e73..f2be630f711b440d24aa8343d5665e14fa82b356 100644 (file)
--- a/src/os/filestore/FileStore.cc
+++ b/src/os/filestore/FileStore.cc
@@ -2942,7 +2942,14 @@ void FileStore::_do_transaction(
       if (r == -ENOENT && !(op->op == Transaction::OP_CLONERANGE ||
                            op->op == Transaction::OP_CLONE ||
                            op->op == Transaction::OP_CLONERANGE2 ||
-                           op->op == Transaction::OP_COLL_ADD))
+                           op->op == Transaction::OP_COLL_ADD ||
+                           op->op == Transaction::OP_SETATTR ||
+                           op->op == Transaction::OP_SETATTRS ||
+                           op->op == Transaction::OP_RMATTR ||
+                           op->op == Transaction::OP_OMAP_SETKEYS ||
+                           op->op == Transaction::OP_OMAP_RMKEYS ||
+                           op->op == Transaction::OP_OMAP_RMKEYRANGE ||
+                           op->op == Transaction::OP_OMAP_SETHEADER))
        // -ENOENT is normally okay
        // ...including on a replayed OP_RMCOLL with checkpoint mode
        ok = true;