I have a distributed volume formed by 4 nodes. When one node goes down, the volume becomes read-only, and I manually remove the broken brick from the volume, which after becomes read-write again, with total capacity reducing to 3/4. After the broken node recovered, I re-add the brick back to the volume, with no error reported, and 'gluster volume status' shows all 4 bricks are Online. But the

deni: Despite the fact that friendly greetings are nice, please ask your question. Carefully identify your problem in such a way that when a volunteer has a few minutes, they can offer you a potential solution. These are volunteers, so be patient. Answers may come in a few minutes, or may take hours. If you're still in the channel, someone will eventually offer an answer.

"Since Gluster volume snapshot is based out of LVM snapshot, each Gluster volume brick should be mapped to an independent thinly provisioned LVM. Also this thinly provisioned LVM should not be used for any other purpose."

there is some options for small files ? i have about 700GB of static files and i would like to increase the write perfomance on this volume, the write perfomance is so poor, im using distributed volume

i'm getting a weird issues using nfs to access gluster. not using any replication, just a single copy. but when a client using nfs tries to create a file it says "file not found", that client can see all the other files in a directory. when using gluster volume i am able to create the files just fine. in fact, the problematic client can write to a tmp folder using nfs and gluster, so it is just affecting some folder/filenames