Hide Forgot
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
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
Files lies on gs9 bricks. T files also lies on gs9 bricks.
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
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