[Bugs] [Bug 1273956] New: status clients should show client version

bugzilla at redhat.com bugzilla at redhat.com
Wed Oct 21 15:09:21 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1273956

            Bug ID: 1273956
           Summary: status clients should show client version
           Product: GlusterFS
           Version: 3.7.4
         Component: glusterd
          Assignee: bugs at gluster.org
          Reporter: joe at julianfamily.org
                CC: bugs at gluster.org, gluster-bugs at redhat.com



I tried to set the read-subvolume to work around a different bug:

$ gluster volume set public cluster.read-subvolume public-client-0              
volume set: failed: One or more connected clients cannot support the feature
being set. These clients need to be upgraded or disconnected before running
this command again

(Odd since read-subvolume has been in since 2.0)

So I looked to see what clients were connected:
$ gluster volume status public clients
Client connections for volume public
----------------------------------------------
Brick : strabo:/data/gluster/fileshare/public
Clients connected : 6
Hostname                                               BytesRead   
BytesWritten
--------                                               ---------   
------------
192.168.2.100:65530                                       124640         
121188
192.168.2.101:65529                                        84624        
1311300
192.168.2.8:65523                                            960            
600
192.168.2.30:65497                                           964            
600
192.168.2.3:65517                                           4076           
3596
192.168.2.30:65518                                         29372          
18264
----------------------------------------------
Brick : nightshade:/data/gluster/fileshare/public
Clients connected : 4
Hostname                                               BytesRead   
BytesWritten
--------                                               ---------   
------------
192.168.2.30:65501                                          4088           
3616
192.168.2.8:65527                                            964            
608
192.168.2.3:65514                                            960            
608
192.168.2.30:65523                                         31840          
20916
----------------------------------------------

Which doesn't tell me which client could be the problem. Reporting the version,
or at least the max-op-version, would be useful.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list