search for: io_u

...mount.glusterfs same volume on different server (not VM), running Ubuntu Xenial and gluster client 3.10.5. mount -t glusterfs -o backupvolfile-server=10.0.1.202 10.0.1.201:/gv_openstack_1 /mnt/gv_openstack_1/ I ran fio job I described earlier. As soon as I killall glusterfsd, fio reported: fio: io_u error on file /mnt/gv_openstack_1/fio.data: Transport endpoint is not connected: read offset=7022575616, buflen=262144 fio: pid=7205, err=107/file:io_u.c:1582, func=io_u error, error=Transport endpoint is not connected And crashed. I still cannot believe I am the only one experiencing these proble...

Pavel. Is there a difference between native client (fuse) and libgfapi in regards to the crashing/read-only behaviour? We use Rep2 + Arb and can shutdown a node cleanly, without issue on our VMs. We do it all the time for upgrades and maintenance. However we are still on native client as we haven't had time to work on libgfapi yet. Maybe that is more tolerant. We have linux VMs mostly

...server (not VM), > running Ubuntu Xenial and gluster client 3.10.5. > > mount -t glusterfs -o backupvolfile-server=10.0.1.202 > 10.0.1.201:/gv_openstack_1 /mnt/gv_openstack_1/ > > I ran fio job I described earlier. As soon as I killall glusterfsd, > fio reported: > > fio: io_u error on file /mnt/gv_openstack_1/fio.data: Transport > endpoint is not connected: read offset=7022575616, buflen=262144 > fio: pid=7205, err=107/file:io_u.c:1582, func=io_u error, > error=Transport endpoint is not connected > > And crashed. I still cannot believe I am the only one e...