Re: mount_dir value seems clobbered in all /var/lib/glusterd/vols/<vol-name>/bricks/<node-name>:<brick-path> files

Avra Sengupta <asengupt@xxxxxxxxxx> · Fri, 5 Aug 2016 11:25:22 +0530



    Hi Milind,

      
      Are the bricks lvm mounterd bricks. This field is populated for
      lvm mounted bricks, and used by them. For regular bricks, which
      don't have a mount point this valus is ignored.

      
      Regards,

      Avra

      
      On 08/04/2016 07:44 PM, Atin Mukherjee wrote:

    
            glusterd_get_brick_mount_dir () does a brick_dir++ 
              which seems to cause this problem and removing this line
              fixes the problem. Commit f846e54b introduced it. 

              
            Ccing Avra/Rajesh

            
          mount_dir is used by snapshot, however I am just wondering how
          are we surviving this case.

          
        ~Atin

      
        On Thu, Aug 4, 2016 at 5:39 PM, Milind
          Changire <mchangir@xxxxxxxxxx>
          wrote:

          here's one
            of the brick definition files for a volume named "twoXtwo"

            
            [root@f24node0 bricks]# cat
            f24node1\:-glustervols-twoXtwo-dir

            hostname=f24node1

            path=/glustervols/twoXtwo/dir

            real_path=/glustervols/twoXtwo/dir

            listen-port=0

            rdma.listen-port=0

            decommissioned=0

            brick-id=twoXtwo-client-1

            mount_dir=/lustervols/twoXtwo/dir          <-- shouldn't
            the value be

                                                         
             /glustervols/...

                                                           there's a
            missing 'g'

                                                           after the
            first '/'

            snap-status=0

            
            This *should* happen for all volumes and for all such brick
            definition

            files or whatever they are called.

            BTW, I'm working with the upstream mainline sources, if that
            helps.

            
            I'm running a 2x2 distribute-replicate volume.

            4 nodes with 1 brick per node.

            1 brick for the hot tier for tiering.

            
            As far as I can tell, I haven't done anything fancy with the
            setup.

            And I have confirmed that there is no directory named
            '/lustervols'

            on any of my cluster nodes.

                
                -- 

                Milind

                _______________________________________________

                Gluster-devel mailing list

                Gluster-devel@xxxxxxxxxxx

                http://www.gluster.org/mailman/listinfo/gluster-devel

              
        -- 

        
            --Atin

          
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel