Description of problem: ======================= With the latest code, observed that the volume information files are missing two fields "op-version" and "client-op-version" which might lead to client disconnects. [root@inception ~]# gluster v list vol0 vol1 vol2 vol3 [root@inception ~]# cat /var/lib/glusterd/vols/vol1/info | grep op-version [root@inception ~]# Version-Release number of selected component (if applicable): ============================================================= glusterfs-3.6.0.27-1.el6rhs.x86_64 How reproducible: ================= 1/1 Steps to Reproduce: ===================== 1. Create a volume 2. Check the info file Actual results: =============== op-version and client-op-version is missing Expected results: ================= op-version and client-op-version should be updated.
This is a down-stream only issue, introduced as part of some backward compatibility fixes for 2.1. A function call to write the said options is missed. The fix is quite trivial and non-intrusive
Fix at https://code.engineering.redhat.com/gerrit/30623
verified with build: glusterfs-3.6.0.28-1.el6rhs.x86_64 op-version and client-op-version are updated in the info [root@inception ~]# cat /var/lib/glusterd/vols/vol0/info | grep version version=2 op-version=30000 client-op-version=30000 [root@inception ~]# [root@inception ~]# cat /var/lib/glusterd/vols/vol0/info type=2 count=4 status=1 sub_count=2 stripe_count=1 replica_count=2 version=2 transport-type=0 volume-id=fa39214a-12d9-4d84-bbbc-7db3f7d3a3f6 username=79cdeb28-bcf0-44ba-ab22-488228356e78 password=2a21bd57-8546-42ee-bc23-084167fe1f96 op-version=30000 client-op-version=30000 parent_volname=N/A restored_from_snap=00000000-0000-0000-0000-000000000000 snap-max-hard-limit=256 performance.readdir-ahead=on brick-0=inception.lab.eng.blr.redhat.com:-rhs-brick1-b1 brick-1=rhs-arch-srv2.lab.eng.blr.redhat.com:-rhs-brick1-b1 brick-2=rhs-arch-srv3.lab.eng.blr.redhat.com:-rhs-brick1-b1 brick-3=rhs-arch-srv4.lab.eng.blr.redhat.com:-rhs-brick1-b1 [root@inception ~]# [root@inception ~]# [root@inception ~]# Moving the bug to verified state
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-1278.html