Bug 1230694
| Summary: | [Backup]: Glusterfind pre fails with htime xattr updation error resulting in historical changelogs not available | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Kotresh HR <khiremat> |
| Component: | glusterfind | Assignee: | Kotresh HR <khiremat> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | bugs <bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.7.1 | CC: | avishwan, bugs, khiremat, mchangir, sanandpa, vorpal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.7.2 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1230015 | Environment: | |
| Last Closed: | 2015-06-20 09:50:52 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: | |
| Embargoed: | |||
| Bug Depends On: | 1228495, 1230015 | ||
| Bug Blocks: | 1223636 | ||
|
Description
Kotresh HR
2015-06-11 11:50:07 UTC
REVIEW: http://review.gluster.org/11181 (features/changelog: Do htime setxattr without XATTR_REPLACE flag) posted (#3) for review on release-3.7 by Kotresh HR (khiremat) COMMIT: http://review.gluster.org/11181 committed in release-3.7 by Vijay Bellur (vbellur) ------ commit 1b7721817a7807bc0af51d89d61fbb723769b2d3 Author: Kotresh HR <khiremat> Date: Tue Jun 9 10:44:44 2015 +0530 features/changelog: Do htime setxattr without XATTR_REPLACE flag HTIME_KEY marks the last changelog rolled over. The xattr is maintained on .glusterfs/changelog/htime/HTIME.TSTAMP file. On every rollover of the changelog file, the xattr is updated. It is being updated with XATTR_REPLACE flag as xattr gets created during changelog enable. But it is once found that the xattrs on the file is cleared and is not reproduced later on. This patch protects that case, if it happens by setting xattr without XATTR_REPLACE flag in failure case. The reason behind doing this in failure case is not to mask the actual cause of xattrs getting cleared. This provides the log message if the original issue still exists but the consequential effects are fixed. Also changed the log messages to depict the events happened during changelog enable. Change-Id: I699ed09a03667fd823d01d65c9c360fa7bc0e455 BUG: 1230694 Reviewed-On: http://review.gluster.org/#/c/11150/ Signed-off-by: Kotresh HR <khiremat> Reviewed-on: http://review.gluster.org/11181 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur> This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.2, please reopen this bug report. glusterfs-3.7.2 has been announced on the Gluster Packaging mailinglist [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://www.gluster.org/pipermail/packaging/2015-June/000006.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user I am still seeing this bug in 3.7.4 Well, we're seeing an error that historical changelogs are unavailable. The cause looks like it's different. |