On Fri, Sep 17, 2021 at 8:19 AM Joshua West <josh@xxxxxxx> wrote: > > Thanks Patrick, > > Similar to Robert, when trying that, I simply receive "Error EINVAL: > adding a feature requires a feature string" 10x times. > > I attempted to downgrade, but wasn't able to successfully get my mons > to come back up, as they had quincy specific "mon data structure > changes" or something like that. > So, I've settled into "17.0.0-6762-g0ff2e281889" on my cluster. > > cephfs is still down all this time later. (Good thing this is a > learning cluster not in production, haha) Yes, sorry the command should have been (note for other readers, please do not blindly do this): ceph fs compat add_incompat 1 "base v0.20" ceph fs compat add_incompat 2 "client writeable ranges" ceph fs compat add_incompat 3 "default file layouts on dirs" ceph fs compat add_incompat 4 "dir inode in separate object" ceph fs compat add_incompat 5 "mds uses versioned encoding" ceph fs compat add_incompat 6 "dirfrag is stored in omap" ceph fs compat add_incompat 7 "mds uses inline data" ceph fs compat add_incompat 8 "no anchor table" ceph fs compat add_incompat 9 "file layout v2" ceph fs compat add_incompat 10 "snaprealm v2" > I began to feel more and more that the issue was related to a damaged > cephfs, from a recent set of server malfunctions on a single node > causing mayhem on the cluster. No, it's not related. The fs was not damaged in any way from this situation. -- Patrick Donnelly, Ph.D. He / Him / His Principal Software Engineer Red Hat Sunnyvale, CA GPG: 19F28A586F808C2402351B93C3301A3E258DD79D _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |