Bug 987432 - mark dht_linkfile creation/deletion fop's as internal
Summary: mark dht_linkfile creation/deletion fop's as internal
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterfs
Version: 2.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: shishir gowda
QA Contact: shishir gowda
URL:
Whiteboard:
Depends On: 987428
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-23 11:29 UTC by shishir gowda
Modified: 2013-12-09 01:36 UTC (History)
7 users (show)

Fixed In Version: glusterfs-3.4.0.12rhs.beta6-1
Doc Type: Bug Fix
Doc Text:
Clone Of: 987428
Environment:
Last Closed: 2013-09-23 22:35:56 UTC
Embargoed:


Attachments (Terms of Use)

Description shishir gowda 2013-07-23 11:29:45 UTC
+++ This bug was initially created as a clone of Bug #987428 +++

Description of problem:

Currently dht creates/deletes linkfiles for various ops like
rename/linking and when layout changes. dht_linkfile_create
already sends a key GLUSTERFS_INTERNAL_FOP_KEY in dict to
identify this as an internal fop and not user based op.

Enhancing rename related links/unlinks to send this key too.
Marker/changelog or other xlators can now identify these as
internal fops and handle them accordingly

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Anand Avati on 2013-07-23 07:27:28 EDT ---

REVIEW: http://review.gluster.org/5335 (cluster/dht: mark linkfile creation/deletion as internal fop) posted (#2) for review on master by Shishir Gowda (sgowda)

Comment 3 Amar Tumballi 2013-08-09 07:14:54 UTC
This is a change in the code, not visible to the users. Hence, doesn't have any proper use-cases to test against.

Comment 6 shishir gowda 2013-08-27 09:17:06 UTC
This is an internal fix of sending additional flag in xdata argument of few fops to identify the fop as being done internally.
Moving the bug to verified state.

Comment 7 Scott Haines 2013-09-23 22:35:56 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. 

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1262.html


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