Hello, Tried it: *$ gluster volume remove-brick GV2Data replica 1 office-wx-hv1-lab-gfs:/mnt/**LogGFSData/brick force* Running remove-brick with cluster.force-migration enabled can result in data corruption. It is safer to disable this option so that files that receive writes during migration are not migrated. Files that are not migrated can then be manually copied after the remove-brick commit operation. Do you want to continue with your current cluster.force-migration settings? (y/n) y volume remove-brick start: failed: need 2(xN) bricks for reducing replica count of the volume from 3 to 1 - Gilboa On Tue, Jul 19, 2022 at 11:36 PM Strahil Nikolov <hunter86_bg@yahoo.com> wrote:
Replacing a dead brick in a 2+1 scenario (2 data + 1 arbiter brick) requires to reduce the replica to 1 by removing the dead brick and the arbiter. Use the force option as you are not using a distributed-replicated volume .
Best Regards, Strahil Nikolov
On Mon, Jul 18, 2022 at 11:36, Patrick Hibbs <hibbsncc1701@gmail.com> wrote: _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/XIA6UN3ULXCN55...