Bug 1288400

Summary:	Handling char type file in the tier volume
Product:	[Community] GlusterFS	Reporter:	Jiffin <jthottan>
Component:	tiering	Assignee:	bugs <bugs>
Status:	CLOSED WONTFIX	QA Contact:	bugs <bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	bugs, rkavunga
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1288401 (view as bug list)		Environment:
Last Closed:	2018-11-02 08:13:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1288401, 1288403

Description Jiffin 2015-12-04 06:25:49 UTC

Description of problem:
In the tier volume char type file is not handled properly

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


How reproducible:
always

Steps to Reproduce:
1.Create a volume
2.Mount the volume 
two issues
3.i)run fstress test on the mount, at the backend char type files can be seen in hot tier only(no corresponding link file is created at cold tier) , so every following fops will fail on that file

3.ii) create char type file in the mount, these files are initially created in cold tier, but after specific amount of time they being promoted to hot tier(creating link file in cold tier)

Actual results:
char type file is not handled properly in tier volume

Expected results:
Should be treated like regular file.
 


Additional info:

Comment 1 Mike McCune 2016-03-28 22:22:31 UTC

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 3 Amar Tumballi 2018-11-02 08:13:19 UTC

Patch https://review.gluster.org/#/c/glusterfs/+/21331/ removes tier functionality from GlusterFS. 

https://bugzilla.redhat.com/show_bug.cgi?id=1642807 is used as the tracking bug for this. Recommendation is to convert your tier volume to regular volume (either replicate, ec, or plain distribute) with "tier detach" command before upgrade, and use backend features like dm-cache etc to utilize the caching from backend to provide better performance and functionality.