A quick fix is to run this command:
sudo brctl setageing br0 0
This causes the aging of the MAC address to time out immediately or in 0 seconds, which delete the entry frmo the FDB (Forwarding Database) and causes the error to go away. The default time is 300 seconds or 5 minutes.
You can also add it under your br0 definition like this in /etc/network/interfaces to make it permanent and automatic:
auto br........
This can be used on almost anything, since Gluster is a userspace tool, based on FUSE. This means that all Gluster appears as to any application is just a directory.
Applications don't need specific support for Gluster, so long as you can tell the application to use a certain directory for storage.
One application can be for redundant and scaled storage, including for within Docker and Kubernetes, LXC, Proxmox, OpenStack, etc or just your image/web/video files or even da........
This was a surprising bug but I unplugged all drives for an array md127. At first it was just 1 drive and mdadm seemed to notice this. I unplugged the second drive taking the array offline but mdadm did not realize it was offline and still showed a non-existent disk as being part of it. This created problems trying to unmount it or even to stop this array with mdadm freezing.
As for how to fix it I can only think of making sure you are not in a mounted path of........