Ravishankar N wrote:
> Unless "replica_0_files_list=( $B0/${V0}1/* )" in NetBSD lists files
> with complete path? It doesn't in Linux.
Right, this is the difference: original script uses
replica_0_files_list=(`ls $B0/${V0}1`)
I use this because NetBSD's ls lists dot files when run as root:
re
On 03/16/2015 09:42 AM, Ravishankar N wrote:
On 03/16/2015 09:44 AM, Emmanuel Dreyfus wrote:
Then there is something I do not get. Here is the section that creates
the split brain. It does not goes through $M0, but directly through
bricks backends in $B0, and moreover during glusterfsd downtim
On 03/16/2015 09:44 AM, Emmanuel Dreyfus wrote:
Then there is something I do not get. Here is the section that creates
the split brain. It does not goes through $M0, but directly through
bricks backends in $B0, and moreover during glusterfsd downtime. How
could pending xattr appear?
We do a "cd
Ravishankar N wrote:
> No, the IO is done from the mount point, so there will be pending afr
> xattrs.
Then there is something I do not get. Here is the section that creates
the split brain. It does not goes through $M0, but directly through
bricks backends in $B0, and moreover during glusterfsd
On 03/15/2015 08:27 PM, Emmanuel Dreyfus wrote:
Emmanuel Dreyfus wrote:
NetBSD passes the tests because before the test can fail, the client
goes into afr_inode_refresh_done(), where spit brain is detected and
repaired by syntask with a afr_refresh_selfheal_wrap() callback.
Here is how I und
Emmanuel Dreyfus wrote:
> NetBSD passes the tests because before the test can fail, the client
> goes into afr_inode_refresh_done(), where spit brain is detected and
> repaired by syntask with a afr_refresh_selfheal_wrap() callback.
Here is how I understand it: the split brain has been created b
Hello
split-brain-healing.t always fail on NetBSD on test 17: after we took
down bricks, modifed files in the backend and restarted everything, we
test that we indeed produced a split brain:
### Acessing the files should now give EIO.
TEST ! cat file1
NetBSD passes the tests because
