Bug 1241529
| Summary: | BitRot :- Files marked as 'Bad' should not be accessible from mount | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Raghavendra Bhat <rabhat> |
| Component: | bitrot | Assignee: | Raghavendra Bhat <rabhat> |
| Status: | CLOSED EOL | QA Contact: | |
| Severity: | high | Docs Contact: | bugs <bugs> |
| Priority: | medium | ||
| Version: | 3.7.2 | CC: | amukherj, bhubbard, bugs, mzywusko, rabhat, racpatel, smohan |
| Target Milestone: | --- | Keywords: | Regression, Reopened, Triaged |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.7.3 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1210689 | Environment: | |
| Last Closed: | 2017-03-08 10:54:34 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: | 1210689 | ||
| Bug Blocks: | 1186580, 1236289 | ||
|
Description
Raghavendra Bhat
2015-07-09 12:23:39 UTC
REVIEW: http://review.gluster.org/11603 (features/bit-rot-stub: deny access to bad objects) posted (#1) for review on release-3.7 by Raghavendra Bhat (raghavendra) REVIEW: http://review.gluster.org/11604 (features/bit-rot-stub: do not allow setxattr and removexattr on bit-rot xattrs) posted (#1) for review on release-3.7 by Raghavendra Bhat (raghavendra) REVIEW: http://review.gluster.org/11603 (features/bit-rot-stub: deny access to bad objects) posted (#2) for review on release-3.7 by Raghavendra Bhat (raghavendra) COMMIT: http://review.gluster.org/11603 committed in release-3.7 by Venky Shankar (vshankar) ------ commit 5144d3d5a4982a86f46ef023d0dc836d0fdead58 Author: Raghavendra Bhat <raghavendra> Date: Tue May 26 19:22:14 2015 +0530 features/bit-rot-stub: deny access to bad objects Backport of http://review.gluster.org/11126 * Access to bad objects (especially operations such as open, readv, writev) should be denied to prevent applications from getting wrong data. * Do not allow anyone apart from scrubber to set bad object xattr. * Do not allow bad object xattr to be removed. Change-Id: I6903184ab64a9d1ea595330b603935979c33bc26 BUG: 1241529 Reviewed-on: http://review.gluster.org/11603 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Venky Shankar <vshankar> COMMIT: http://review.gluster.org/11604 committed in release-3.7 by Venky Shankar (vshankar) ------ commit 94b0109a8ed55d5aebe0604ffb19cbb583797cf5 Author: Raghavendra Bhat <raghavendra> Date: Wed Jun 24 20:06:01 2015 +0530 features/bit-rot-stub: do not allow setxattr and removexattr on bit-rot xattrs Backport of http://review.gluster.org/11389 * setxattr and {f}removexattr of versioning, signature and bad-file xattrs are returned with error. Change-Id: I8fe5f973d6e410bec2758959d20d379189808d5e BUG: 1241529 Signed-off-by: Raghavendra Bhat <raghavendra> Reviewed-on: http://review.gluster.org/11604 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Venky Shankar <vshankar> 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.3, please open a new bug report. glusterfs-3.7.3 has been announced on the Gluster mailinglists [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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/12078 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user 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.3, please open a new bug report. glusterfs-3.7.3 has been announced on the Gluster mailinglists [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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/12078 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user Reopening since I see this on the latest nightly.
glusterfs-3.7.5-12.el6rhs.x86_64
# getfattr -d -e hex -m. /rhgs/brick3/etc/prelink.cache
getfattr: Removing leading '/' from absolute path names
# file: rhgs/brick3/etc/prelink.cache
security.selinux=0x756e636f6e66696e65645f753a6f626a6563745f723a64656661756c745f743a733000
trusted.afr.dirty=0x000000000000000000000000
trusted.bit-rot.bad-file=0x3100
trusted.bit-rot.signature=0x01020000000000000084ff92691f909a05b224e1c56abb4864f01b4f8e3c854e4bb4c7baf1d3f6d652
trusted.bit-rot.version=0x02000000000000005678d5e20008117f
trusted.gfid=0x79e7925db5a548cdada2e7f9817c4f12
# head -1 /mnt/glustermounts/etc/prelink.cache
prelink-ELF0.3.2�'/�
V,� ��xV�ĨU�V
�xV�N:�Vٹ�SJ�1%�>B�xV�U@21◆2±�
&�T┐>B�│V��2�2���│VYӃ>B�│VV>C�│VR�� GߢS��
�│V�N �!>C�│V�▮#L�$>C�│V���U1�6�│V7VE�7_C�│V:KK2P� 2]�:>C�│V��)L⎽�@>C�│V�T��D
2��Q┌�│VJ3�UDŽR├�│VP¸UلS┘�│V�3BVTb�│VL�U��>C�│VP@2#◆2"�X>C�│V��↓�[>C�│V�L�°>C�│V°�S▒�┐>C�│V�U├�┼>C�│VV��─�│VٖCK��⎼�│VGߢSՅ⎽>C�│V↑┘┬�│Vė\U��│�│V3S
No EIO.
Could you have a look at this and decide what to do with this bug? Hi Brad Hubbard, In case of replica volume if all copies are bad then only EIO error comes,and any of the copy is good read/write will be served from that copy In your case all copies are bad ? (In reply to RajeshReddy from comment #10) > Hi Brad Hubbard, > > In case of replica volume if all copies are bad then only EIO error > comes,and any of the copy is good read/write will be served from that copy > > In your case all copies are bad ? It was only by luck I saw this. If you need my input set NEEDINFO on me. This was nearly six months ago and I don't remember the circumstances or details. This is te problem with requesting feedback 6 months later. This bug is getting closed because GlusteFS-3.7 has reached its end-of-life. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |