| Summary: | Quota: the local mount on server fails while using quota list command | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Saurabh <saurabh> |
| Component: | quota | Assignee: | Amar Tumballi <amarts> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | mainline | CC: | amarts, gluster-bugs, pkarampu, raghavendra, vraman |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Saurabh
2011-04-12 14:09:52 UTC
This bug is not seen on my laptop on master. Can we close this bug as resolved? regards, Raghavendra. In the volume I was already having data, and enabled/set quota limits. The earlier data is not been taken care. [root@centos-qa-client-2 sbin]# ./gluster volume quota dist4 list path limit_set size ---------------------------------------------------------------------------------- / 1048576 0 I remember earlier that it was showing the size. (In reply to comment #0) > As discussed with dev. > > This condition happened only for one volume and only for brick, > > > [root@centos-qa-client-2 sbin]# ./gluster volume quota dist2 list > path limit_set size > ---------------------------------------------------------------------------------- > / 2MB > /d1 1MB > /d2 1MB > /d2/dd2 100KB > /d1/dd1 100KB > umount: /tmp/mntCX0iYD: not mounted Steps to reproduce: kill glusterd when the response hits the cli for this command, the mounts done by cli will exit because glusterd is not running anymore saying the following but return '0', so the cli proceeds thinking it mounted the fuse client successfully and prints this error on unmount. [2011-04-16 12:41:19.131078] E [socket.c:1685:socket_connect_finish] 0-glusterfs: connection to failed (Connection refused) [2011-04-16 12:41:19.131211] E [glusterfsd-mgmt.c:740:mgmt_rpc_notify] 0-glusterfsd-mgmt: failed to connect with remote-host: Transport endpoint is not connected [2011-04-16 12:41:19.131398] W [glusterfsd.c:700:cleanup_and_exit] (-->/usr/local/lib/libgfrpc.so.0(rpc_transport_notify+0x130) [0x7ffff795bab4] (-->/usr/local/lib/libgfrpc.so.0(rpc_clnt_notify+0x203) [0x7ffff795f41a] (-->/usr/local/sbin/glusterfs() [0x40924f]))) 0-: received signum (1), shutting down [2011-04-16 12:41:19.131440] I [fuse-bridge.c:3688:fini] 0-fuse: Unmounting '/tmp/mnt3SoIAM'. Pranith PATCH: http://patches.gluster.com/patch/6913 in master (cli: check for connectivity before doing mount) didn't find the umount issue happening again on qa-14 release |