Bug 1285730 - Tier: Hard link created during file promotion is lost once the migration is complete
Summary: Tier: Hard link created during file promotion is lost once the migration is c...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: tier
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: hari gowtham
QA Contact: Sweta Anandpara
URL:
Whiteboard: tier-migration
Depends On: 1282710
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-26 11:00 UTC by Nithya Balachandran
Modified: 2018-11-08 19:18 UTC (History)
4 users (show)

Fixed In Version: glusterfs-3.7.5-19
Doc Type: Bug Fix
Doc Text:
Clone Of: 1282710
Environment:
Last Closed: 2018-11-08 19:18:29 UTC
Embargoed:


Attachments (Terms of Use)

Description Nithya Balachandran 2015-11-26 11:00:03 UTC
+++ This bug was initially created as a clone of Bug #1282710 +++

Description of problem:

A hard link created when a file is being promoted will be lost once the file migration is complete.

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


How reproducible:

Consistently

Steps to Reproduce:
1. Create a tier volume and FUSE mount it.
2. Create a large file FILE1 so it will take some time to migrate. This is created on the hot tier by default
3. After FILE1 is demoted, append some data to it to trigger file promotion
4. While FILE1 is being promoted, create a hardlink hlink to FILE1 in some other directory


Actual results:
Once FILE1 has been migrated, hlink no longer exists

Expected results:
Once FILE1 has been migrated, hlink should still exist

Additional info:

--- Additional comment from Vijay Bellur on 2015-11-17 10:03:56 EST ---

REVIEW: http://review.gluster.org/12600 (WIP cluster/tier : hardlink creation fails) posted (#1) for review on master by N Balachandran (nbalacha)

Comment 8 hari gowtham 2018-11-08 19:18:29 UTC
As tier is not being actively developed, I'm closing this bug. Feel free to open it if necessary.


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