search for: libfgapi

...different values for total and used/free space of a volume when accessed through libgfapi and when through fuse -- because these values are multiples of f_frsize, and libgfapi uses the native f_frsize of the backend (typically 4k), while fuse provides its synthetic f_frsize (typically 128k). So the libfgapi provided sizes are more granular. OTOH, I couldn't find any program in standard Unix userspace where the implementation commonly used in GNU/Linux would rely on the f_bsize hint. It does not mean there is none -- and then there is of course the vast space of non-standard userland. Possibiliit...

...e.g. HW or Gluster upgrade, reboot) is very scary, > because we often end up with read-only filesystems on all VMs. > > However we use ext4, so I cannot comment on XFS. We use the fuse mount, because we are lazy and haven't upgraded to libgfapi.? I hope to start a new cluster with to libfgapi shortly because of the better performance. Also we use a localhost mount for the gluster driveset on each compute node (i.e. so called hyperconverged). So the only 'gluster' only kit is the lightweight arb box. So those VMs in the gluster 'pool' have a local write and then only 1...

Hi, On Thu, Aug 24, 2017 at 2:13 AM, WK <wkmail at bneit.com> wrote: > The default timeout for most OS versions is 30 seconds and the Gluster > timeout is 42, so yes you can trigger an RO event. I get read-only mount within approximately 2 seconds after failed IO. > Though it is easy enough to raise as Pavel mentioned > > # echo 90 > /sys/block/sda/device/timeout AFAIK

That really isnt an arbiter issue or for that matter a Gluster issue. We have seen that with vanilla NAS servers that had some issue or another. Arbiter simply makes it less likely to be an issue than replica 2 but in turn arbiter is less 'safe' than replica 3. However, in regards to Gluster and RO behaviour The default timeout for most OS versions is 30 seconds and the Gluster