I also noticed the following error in the glusterd.log file today related to quota: [2018-11-01 13:32:06.159865] E [MSGID: 101042] [compat.c:597:gf_umount_lazy] 0-management: Lazy unmount of /var/run/gluster/myvol-private_quota_limit/ [2018-11-01 13:32:06.160251] E [MSGID: 106363] [glusterd-utils.c:12556:glusterd_remove_auxiliary_mount] 0-management: umount on /var/run/gluster/myvol-private_quota_limit/ failed, reason : Success Something must be wrong with the quotas? ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Tuesday, October 30, 2018 6:24 PM, mabi <mabi@xxxxxxxxxxxxx> wrote: > Hello, > > Since I upgraded my 3-node (with arbiter) GlusreFS from 3.12.14 to 4.1.5 I see quite a lot of the following error message in the brick log file for one of my volumes where I have quota enabled: > > [2018-10-21 05:03:25.158311] W [rpc-clnt.c:1753:rpc_clnt_submit] 0-myvol-private-quota: error returned while attempting to connect to host:(null), port:0 > > Is this a bug? should I file a bug report? or does anyone know what is wrong here maybe with my system? > > Best regards, > Mabi _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
