[Bugs] [Bug 1245981] New: forgotten inodes are not being signed

bugzilla at redhat.com bugzilla at redhat.com
Thu Jul 23 09:05:21 UTC 2015


            Bug ID: 1245981
           Summary: forgotten inodes are not being signed
           Product: GlusterFS
           Version: mainline
         Component: bitrot
          Assignee: bugs at gluster.org
          Reporter: rabhat at redhat.com
                CC: bugs at gluster.org
      Docs Contact: bugs at gluster.org

Description of problem:

If a object gets modified, then bit-rot-stub sends a notification to BitD to
sign the object. BitD waits for sometime before signing the object so that if
any modification happens within that time interval, it need not sign multiple
times. And once the object is signed, its inode context is changed to indicate
that, the inode is now in its default state.

But if the inode gets forgotten after sending the sign notification to BitD,
but before getting sign request, then when the sign request comes, the inode
context says inode is in default state (instead of modified state) and does not
sign the object.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

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