Hi,
do you have logs from the MDS? And how exactly did you move the /temp
directory to a different pool? That might help understand what
happened. There was a thread here a couple of weeks ago how about
moving contents to a different CephFS pool.
Zitat von Maxim Goncharov <m...@mit.edu>:
Hi Everyone,
I have a CephFS cluster that has MDS stuck in read only mode, and I
do not know what can be done to return the cluster into the writable
mode:
health: HEALTH_WARN
1 MDSs are read only
1 MDSs behind on trimming
How I got there: we have an FS where we store data in EC pool. We
have one subdirectory that contains a lot of transitory data
(constant write/read/delete). I wanted to put this subdirectory
(let's call it /temp) into a separate replicated pool.
I did: created replicated pool, added it to the FS, switched /temp
to that replicated pool.
All worked for about 24 hours and then became obvious it was not a
good idea, so I reversed all steps: switched /temp to the original
EC pool, removed replicated pool from FS, deleted the replicated pool.
That is when MDS went into read only state. I can see inodes that
were created in /temp when it belonged to the replicated pool.
I tried many different things that I found in documentation, nothing
works. What should I do in order for the FS become writable again?
Thank you, --Max
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
