search for: 933625

Displaying 12 results from an estimated 12 matches for "933625".

2018 Feb 13
2
Failed to get quota limits
...-+ 1: volume myvolume-client-0 2: type protocol/client 3: option opversion 31004 4: option clnt-lk-version 1 5: option volfile-checksum 0 6: option volfile-key myvolume 7: option client-version 3.10.7 8: option process-uuid gfs1a-14348-2018/02/13-08:16:09:933625-myvolume-client-0-0-0 9: option fops-version 1298437 10: option ping-timeout 42 11: option remote-host gfs1a.domain.local 12: option remote-subvolume /data/myvolume/brick 13: option transport-type socket 14: option transport.address-family inet 15: option username bea3...
2018 Feb 13
0
Failed to get quota limits
...2: type protocol/client > 3: option opversion 31004 > 4: option clnt-lk-version 1 > 5: option volfile-checksum 0 > 6: option volfile-key myvolume > 7: option client-version 3.10.7 > 8: option process-uuid > gfs1a-14348-2018/02/13-08:16:09:933625-myvolume-client-0-0-0 > 9: option fops-version 1298437 > 10: option ping-timeout 42 > 11: option remote-host gfs1a.domain.local > 12: option remote-subvolume /data/myvolume/brick > 13: option transport-type socket > 14: option transport.address-family ine...
2018 Feb 13
2
Failed to get quota limits
...4: option clnt-lk-version 1 >>>>> 5: option volfile-checksum 0 >>>>> 6: option volfile-key myvolume >>>>> 7: option client-version 3.10.7 >>>>> 8: option process-uuid >>>>> gfs1a-14348-2018/02/13-08:16:09:933625-myvolume-client-0-0-0 >>>>> 9: option fops-version 1298437 >>>>> 10: option ping-timeout 42 >>>>> 11: option remote-host gfs1a.domain.local >>>>> 12: option remote-subvolume /data/myvolume/brick >>>>> 13:...
2018 Feb 13
2
Failed to get quota limits
...>>>>> 5: option volfile-checksum 0 >>>>>>> 6: option volfile-key myvolume >>>>>>> 7: option client-version 3.10.7 >>>>>>> 8: option process-uuid >>>>>>> gfs1a-14348-2018/02/13-08:16:09:933625-myvolume-client-0-0-0 >>>>>>> 9: option fops-version 1298437 >>>>>>> 10: option ping-timeout 42 >>>>>>> 11: option remote-host gfs1a.domain.local >>>>>>> 12: option remote-subvolume /data/myvolume/br...
2018 Feb 13
0
Failed to get quota limits
...k-version 1 >>>>>> 5: option volfile-checksum 0 >>>>>> 6: option volfile-key myvolume >>>>>> 7: option client-version 3.10.7 >>>>>> 8: option process-uuid >>>>>> gfs1a-14348-2018/02/13-08:16:09:933625-myvolume-client-0-0-0 >>>>>> 9: option fops-version 1298437 >>>>>> 10: option ping-timeout 42 >>>>>> 11: option remote-host gfs1a.domain.local >>>>>> 12: option remote-subvolume /data/myvolume/brick >>>...
2018 Feb 13
0
Failed to get quota limits
...> 5: option volfile-checksum 0 >>>>>>>> 6: option volfile-key myvolume >>>>>>>> 7: option client-version 3.10.7 >>>>>>>> 8: option process-uuid >>>>>>>> gfs1a-14348-2018/02/13-08:16:09:933625-myvolume-client-0-0-0 >>>>>>>> 9: option fops-version 1298437 >>>>>>>> 10: option ping-timeout 42 >>>>>>>> 11: option remote-host gfs1a.domain.local >>>>>>>> 12: option remote-subvolume /...
2018 Feb 12
0
Failed to get quota limits
Hi, Can you provide more information like, the volume configuration, quota.conf file and the log files. On Sat, Feb 10, 2018 at 1:05 AM, mabi <mabi at protonmail.ch> wrote: > Hello, > > I am running GlusterFS 3.10.7 and just noticed by doing a "gluster volume quota <volname> list" that my quotas on that volume are broken. The command returns no output and no errors
2018 Feb 23
2
Failed to get quota limits
...on volfile-checksum 0 >>>>>>>>> 6: option volfile-key myvolume >>>>>>>>> 7: option client-version 3.10.7 >>>>>>>>> 8: option process-uuid >>>>>>>>> gfs1a-14348-2018/02/13-08:16:09:933625-myvolume-client-0-0-0 >>>>>>>>> 9: option fops-version 1298437 >>>>>>>>> 10: option ping-timeout 42 >>>>>>>>> 11: option remote-host gfs1a.domain.local >>>>>>>>> 12: option re...
2018 Feb 27
2
Failed to get quota limits
...option client-version 3.10.7 >> > > > > > > > > > >> > > > > > > > > > 8: option process-uuid >> > > > > > > > > > >> > > > > > > > > > gfs1a-14348-2018/02/13-08:16:09:933625-myvolume-client-0-0-0 >> > > > > > > > > > >> > > > > > > > > > 9: option fops-version 1298437 >> > > > > > > > > > >> > > > > > > > > > 10: option ping-timeout 42 &gt...
2018 Feb 24
0
Failed to get quota limits
...> > 7: option client-version 3.10.7 > > > > > > > > > > > > > > > > > > > > 8: option process-uuid > > > > > > > > > > > > > > > > > > > > gfs1a-14348-2018/02/13-08:16:09:933625-myvolume-client-0-0-0 > > > > > > > > > > > > > > > > > > > > 9: option fops-version 1298437 > > > > > > > > > > > > > > > > > > > > 10: option ping-timeout 42 > > > &g...
2018 Feb 27
0
Failed to get quota limits
....7 > > > > > > > > > > > > > > > > > > > > > > > > 8: option process-uuid > > > > > > > > > > > > > > > > > > > > > > > > gfs1a-14348-2018/02/13-08:16:09:933625-myvolume-client-0-0-0 > > > > > > > > > > > > > > > > > > > > > > > > 9: option fops-version 1298437 > > > > > > > > > > > > > > > > > > > > > > > > 10:...
2018 Feb 09
3
Failed to get quota limits
Hello, I am running GlusterFS 3.10.7 and just noticed by doing a "gluster volume quota <volname> list" that my quotas on that volume are broken. The command returns no output and no errors but by looking in /var/log/glusterfs.cli I found the following errors: [2018-02-09 19:31:24.242324] E [cli-cmd-volume.c:1674:cli_cmd_quota_handle_list_all] 0-cli: Failed to get quota limits for