[Bugs] [Bug 1221914] New: Implement MKNOD fop in bit-rot.

[bugzilla at redhat.com]

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

            Bug ID: 1221914
           Summary: Implement MKNOD fop in bit-rot.
           Product: GlusterFS
           Version: mainline
         Component: bitrot
          Assignee: bugs at gluster.org
          Reporter: kdhananj at redhat.com
                CC: bugs at gluster.org, rabhat at redhat.com,
                    vshankar at redhat.com
      Docs Contact: bugs at gluster.org



Description of problem:
Shard xlator creates new shards using MKNOD fop during inode writes. But bitrot
does not have mknod implemented. Writevs on new shards is failing in bitrot
with EINVAL, with the following message appearing in the brick logs:

[2015-05-15 07:49:20.836176] E [bit-rot-stub.c:989:br_stub_writev]
0-dis-bitrot-stub: failed to get the inode context for the inode
c007285e-c448-455a-a9b5-6c1ca011c3e0

Turns out inode ctx for a file is set by bitrot xlator in create callback
(alone). And it is read in br_stub_writev(). Due to the absence of a
br_stub_mknod() fop through which shards are created, a subsequent writes on
these shards leads to inode_ctx_get() failure leading to bit-rot xlator
unwinding the fop with EINVAL.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

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.