I finally migrated from reef to squid. It went well, but I got a whole chumbucket of obsolete encryption messages. A lot of which were for services and servers that don't exist anymore. So I removed the obvious ones and rotated the rest. It's possible that I may have deleted something related to NFS, but I don't think so. Just for context. NFS itself, which has always been a little wonky stopped working. I tried re-defining it, but ran into issues relating to the infamous "cmount_path" and "user_id" upgrade problems, so I corrected as indicated, giving this:  [    {     "access_type": "RW",     "clients": [       {         "access_type": "RW",         "addresses": [           "10.0.1.0/16",           "192.168.1.0/24"         ],         "squash": "no_root_squash"       }     ],     "cluster_id": "nfs2",     "export_id": 1,     "fsal": {       "fs_name": "ceefs",       "cmount_path": "/",       "name": "CEPH"     },     "path": "/",     "protocols": [       4     ],     "security_label": false,     "squash": "no_root_squash",     "transports": [       "TCP"     ],     "pseudo": "/ceph"   } ] This is the result: ceph nfs export apply nfs -i exports.json [   {     "msg": "Failed to apply export: Expecting value: line 1 column 1 (char 0)",     "pseudo": "/ceph",     "state": "error"   } ] The message itself is a blatant lie or at least totally unhelpful. No matter where I put the pseudo definition in the JSON, the same message appears and if I omit it, it complains that "pseudo" is missing. I deleted the cluster, but the export remains. I cannot delete the export itself because without the cmount_path, the deletion fails. Which is absurd. Of all the times you should be able to delete something this is it. I've been able to create a new NFS cluster using more modern techniques, but it won't let me have any useful exports until I can flush out the previous bad one.