| Summary: | Rebalance is not preserving file access time for some files | ||
|---|---|---|---|
| Product: | Red Hat Gluster Storage | Reporter: | Prasad Desala <tdesala> |
| Component: | replicate | Assignee: | Pranith Kumar K <pkarampu> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Sayalee <saraut> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | rhgs-3.2 | CC: | amukherj, khiremat, nchilaka, pkarampu, ravishankar, rhs-bugs, saraut, storage-qa-internal |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-02-24 16:11:59 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: | |
It's close to two years since this bug has received any updates. What's the plan around this bug? Are we able to hit this in latest releases? If so are we going to address it in coming months? A decision on this bug is highly desirable. Will update the bz based on ctime feature testing. |
Description of problem: ======================= Rebalance is not preserving file access time for some files. File 'f25950' access time is changed by 1sec lag after rebalance. Version-Release number of selected component (if applicable): 3.8.4-3.el7rhgs.x86_64 How reproducible: ================= 2/2 Steps to Reproduce: =================== 1) Create a distributed replicate volume and start it. 2) Fuse mount the volume on a client. 3) From mount, create a very large data set of files. 4) Once the files are created, make a note of file creation time for all the created files. Can be done by capturing the entire 'll' output to a file. ll >> before.txt 5) Without running any IO, add few bricks and trigger rebalance. Wait till the rebalance completes. 6) Once the rebalance is completed, again capture the entire 'll' output to a new file. ll >> after.txt Now, compare the files that are captured before and after rebalance. diff before.txt - after.txt After rebalance, for 'f25950' there is a differ in the file time stamps. < -rw-r--r--. 1 root root 1048576 Nov 10 22:14 f25950 --> Before rebalance --- > -rw-r--r--. 1 root root 1048576 Nov 10 22:13 f25950 --> After rebalance [root@xxx- fuse]# stat f25950 File: ‘f25950’ Size: 1048576 Blocks: 2048 IO Block: 131072 regular file Device: 24h/36d Inode: 10980026696753750608 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Context: system_u:object_r:fusefs_t:s0 Access: 2016-11-10 22:13:59.867829000 +0530 Modify: 2016-11-10 22:13:59.996828000 +0530 Change: 2016-11-10 23:30:07.758420279 +0530 Birth: - Actual results: =============== After rebalance, for 'f25950' there is 1sec difference in the file access time. Expected results: ================= File access time should be preserved after rebalance.