That means you have another librbd client that "owns" the image that you will need to shut down before you can make that change. On Wed, Mar 24, 2021 at 9:01 AM Edgelong Voodu <1070443499cs@xxxxxxxxx> wrote: > > hi， > Thank you for the clarification. > It’s already promoted and not mirrored ,a primary image > I have run rbd —debug-rbd=30 and collect a log file > Which shows locker owner still alive and unable get the lock, return -EAGAIN > I’ll send you log later > > Thank you so much > > > Jason Dillaman <jdillama@xxxxxxxxxx>于2021年3月24日 周三20:55写道： >> >> It sounds like this is a non-primary mirrored image, which means it's >> read-only and cannot be modified. A quick "rbd info" will tell you the >> mirror state. Instead, you would need to force-promote it to primary >> via "rbd mirror image promote --force" before attempting to modify the >> image. >> >> On Wed, Mar 24, 2021 at 3:44 AM Edgelong Voodu <1070443499cs@xxxxxxxxx> wrote: >> > >> > hi , dillaman: >> > i was confused nowadays, when i execute the rbd feature disable <image> journaling, >> > the result of this often shows me : >> > rbd: failed to update image features: (30) Read-only file system >> > i use the rbd-mirror for replicate data between two clouster. i thought the rbd-mirror could be the reason. but i have no idea about it. could you give some advise ? >> > some log when execute rbd command also send you. >> >> >> >> -- >> Jason >> > -- > 发自移动版 Gmail -- Jason _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |