[Bugs] [Bug 1210689] New: BitRot :- Files marked as 'Bad' should not be accessible from mount

bugzilla at redhat.com bugzilla at redhat.com
Fri Apr 10 11:23:37 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1210689

            Bug ID: 1210689
           Summary: BitRot :- Files marked as 'Bad' should not be
                    accessible from mount
           Product: GlusterFS
           Version: mainline
         Component: bitrot
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: racpatel at redhat.com
                CC: bugs at gluster.org
      Docs Contact: bugs at gluster.org



Description of problem:
=======================
If file is marked as 'Bad' then any access to that file from mount should get
'EIO' error till its recovered .(recovery using self heal/EC or manual)


Version-Release number of selected component (if applicable):
=============================================================
3.7dev-0.952.gita7f1d08.el6.x86_64

How reproducible:
=================
always

Steps to Reproduce:
===================
1. create and mount volume.
2. enable bitrot
3. create file
4. modify file from backend(not from mount)
5. Once file is marked as bad, try to access it from mount.

[]# getfattr -d -m .  /pavanbrick3/*/f9 -e hex
getfattr: Removing leading '/' from absolute path names
# file: pavanbrick3/r1/f9
security.selinux=0x756e636f6e66696e65645f753a6f626a6563745f723a64656661756c745f743a733000
trusted.gfid=0xc2ca6098ab304d9c9027df491e07c0f7
trusted.glusterfs.bad-file=0x3100
trusted.glusterfs.bit-rot.signature=0x010000000000000004000000000000009ad89c03b457431979ab5c44131dda04d1bc1652271cc7c37a91c3a10de6a6b0
trusted.glusterfs.bit-rot.version=0x0400000000000000552623db00042680

Actual Result:-
===============
[root at rhs-client37 rac1]# cat f9
new
new
new
new
something
corrupt


Expect Result:-
===============
 Files marked as 'Bad' should not be accessible from mount and user should get
EIO error

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the Docs Contact for the bug.


More information about the Bugs mailing list