Description of problem: While creating a test for thin arbiter volume, I saw a hang while brick was down and we write data on mount point. Steps - 1 - Create plain thin arbiter volume TA 2 - Mount the volume TA 3 - Create a file on mount point . 4 - Kill data brick B1 5 - Write data on file on mount point dd if=/dev/zero of=/mountpoint/a.txt bs=1M count=5 Hang can be seen on mount point Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I think this bug would be solved after with patch sent for two domain lock for write transactions.
The patch for write transaction has been sent and it has fixed the issue. https://review.gluster.org/#/c/glusterfs/+/20095/