[Bugs] [Bug 1744950] glusterfs wrong size with total sum of brick.

bugzilla at redhat.com bugzilla at redhat.com
Wed Aug 28 09:07:46 UTC 2019


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

Sanju <srakonde at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
              Flags|                            |needinfo?(liuruit at gmail.com
                   |                            |)



--- Comment #15 from Sanju <srakonde at redhat.com> ---
As the user is saying he expanded the cluster, I checked the add-brick code
path and I don't see any problem here:

excerpt from glusterd_op_perform_add_bricks : 

                ret = glusterd_resolve_brick (brickinfo);
                if (ret)
                        goto out;

                if (!gf_uuid_compare (brickinfo->uuid, MY_UUID)) {
                        ret = sys_statvfs (brickinfo->path, &brickstat);
                        if (ret) {
                                gf_msg (this->name, GF_LOG_ERROR, errno,
                                        GD_MSG_STATVFS_FAILED,
                                        "Failed to fetch disk utilization "
                                        "from the brick (%s:%s). Please check
the health of "
                                        "the brick. Error code was %s",
                                        brickinfo->hostname, brickinfo->path,
                                        strerror (errno));

                                goto out;
                        }
                        brickinfo->statfs_fsid = brickstat.f_fsid;
                }

Did you upgrade from some older gluster release to 3.12.15? If you have
upgraded from the older version, you are hitting
https://bugzilla.redhat.com/show_bug.cgi?id=1632889. This bug got fixed in
release-6 and backported to release-4 and release-5 branches.

Thanks,
Sanju

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


More information about the Bugs mailing list