Bug 1402773

Summary: [GSS] - T files getting listed on volume mount
Product: Red Hat Gluster Storage Reporter: Bipin Kunal <bkunal>
Component: distributeAssignee: Nithya Balachandran <nbalacha>
Status: CLOSED CURRENTRELEASE QA Contact: Prasad Desala <tdesala>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhgs-3.1CC: amukherj, bkunal, moagrawa, rhs-bugs, storage-qa-internal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-09 07:12:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Bipin Kunal 2016-12-08 10:17:36 UTC
Description of problem: T files getting listed on volume mount point as well


Version-Release number of selected component (if applicable):
-3.7.1-11.el6rhs.x86_64 

How reproducible:

Not reproducible


Actual results:
From volume mount :
# ll /tmp/mount/diva/INFORMATIVOS_MS/divastorage/DIVA/0005/989/697
total 1870135
-rw-rwxr-T 1 diva diva 1915017728 Nov 29 14:56 00000001
-rw-rwxr-- 1 diva diva 1915017728 May 31  2015 00000001
-rw-rwxr-T 1 diva diva        161 Nov 29 14:56 index.txt
-rw-rwxr-- 1 diva diva        161 May 31  2015 index.txt


Expected results:
# ll /tmp/mount/diva/INFORMATIVOS_MS/divastorage/DIVA/0005/989/697
total 1870135
-rw-rwxr-- 1 diva diva 1915017728 May 31  2015 00000001
-rw-rwxr-- 1 diva diva        161 May 31  2015 index.txt

Additional info:


ll /datos/brick2/data/diva/INFORMATIVOS_MS/divastorage/DIVA/0005/989/697:
total 0
-rw-rwxr-T+ 2 diva diva 1915017728 Nov 29 14:56 00000001
-rw-rwxr-T+ 2 diva diva        161 Nov 29 14:56 index.txt

ll /datos/brick5/data/diva/INFORMATIVOS_MS/divastorage/DIVA/0005/989/697:
total 1870140
-rw-rwxr--+ 2 diva diva 1915017728 May 31  2015 00000001
-rw-rwxr--+ 2 diva diva        161 May 31  2015 index.txt

Comment 7 Mohit Agrawal 2016-12-08 12:44:28 UTC
Hi,

As per log shared in C#3 rebalance is failing at the time of checking disk space and (.....T) file is created by function __dht_rebalance_create_dst_file and before calling the function __dht_check_free_space to check disk space in code .

In the old release (glusterfs-3.7.1-11.el6rhs.x86_64) there is no code exist to cleanup T file in case of failure as below exist in latest release


>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

       /* reset the destination back to 0 */
        if (clean_dst) {
                lk_ret = syncop_ftruncate (to, dst_fd, 0, NULL, NULL);
                if (lk_ret) {
                        gf_msg (this->name, GF_LOG_ERROR, -lk_ret,
                                DHT_MSG_MIGRATE_FILE_FAILED,
                                "Migrate file failed: "
                                "%s: failed to reset target size back to 0",
                                loc->path);
                }
        }


>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

So i believe it is expected behavior and issue will resolve after upgrade the package.

Regards
Mohit Agrawal

Comment 11 Bipin Kunal 2016-12-08 15:01:19 UTC
Files lies on gs9 bricks. T files also lies on gs9 bricks.

Comment 12 Mohit Agrawal 2016-12-09 07:00:37 UTC
Hi,

 we have found the root cause why T file is visible on mount point.The issue will happen in case only when a user has set any ACL on file before start migration.
The issue is already known(https://bugzilla.redhat.com/show_bug.cgi?id=1234610) and it is fixed from Errata (https://rhn.redhat.com/errata/RHSA-2015-1845.html) so i believe it will resolve after upgrade the package.

Regards
Mohit Agrawal

Comment 13 Bipin Kunal 2016-12-09 07:12:18 UTC
Thanks for the information Mohit.

Everything seems clear now, 

Why T files are getting listed :
    As they have permission set, They are getting listed 

Why is permission set for T file :

    This is well answered in https://bugzilla.redhat.com/show_bug.cgi?id=1234610

As this issue is fixed in newer release, I will close this bug.

Thanks,
Bipin Kunal