Bug 1615795 - Trash xlator do not send the gfid in the dict while recursively creating dirs
Summary: Trash xlator do not send the gfid in the dict while recursively creating dirs
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: trash-xlator
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-14 09:27 UTC by Karthik U S
Modified: 2018-08-24 04:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-24 04:37:27 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Karthik U S 2018-08-14 09:27:06 UTC
Description of problem:
When trash xlator tries to create directories recursively inside .trashcan as part of the trash_truncate_mkdir_cbk() function, it does not send the gfid to be set for the newly created directory in the dictionary. When posix_gfid_set() function checks for the gfid in the xattr_req dictionary it will not see one being sent there and will return from there. So when we try to send the appropriate error if there is no gfid in the dict, the trash_truncate operation will fail.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
trash xlator should send the gfid xattr value in the dictionary while creating directories recursively as part of trash_truncate_mkdir_cbk().


Additional info:

Comment 1 Pranith Kumar K 2018-08-17 05:25:37 UTC
Anoop,
    How long do you think it will take to fix this issue? Based on that we can take the decision about whether to merge the patch Karthik sent or wait it out.

Let us know.

Pranith

Comment 2 Anoop C S 2018-08-17 06:16:52 UTC
Jiffin had a comment on change 20630:

https://review.gluster.org/c/glusterfs/+/20630#message-80e53c67e1347a855228aa68616dc0bfddccf0b2


Note You need to log in before you can comment on or make changes to this bug.