Bug 1288403 - Handling char type file in the tier volume
Summary: Handling char type file in the tier volume
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: tier
Version: rhgs-3.1
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ---
Assignee: hari gowtham
QA Contact: Nag Pavan Chilakam
URL:
Whiteboard:
Depends On: 1288400 1288401
Blocks: 1286022
TreeView+ depends on / blocked
 
Reported: 2015-12-04 06:28 UTC by Jiffin
Modified: 2018-02-06 17:42 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1288401
Environment:
Last Closed: 2018-02-06 17:42:44 UTC
Embargoed:


Attachments (Terms of Use)

Description Jiffin 2015-12-04 06:28:19 UTC
+++ This bug was initially created as a clone of Bug #1288401 +++

+++ This bug was initially created as a clone of Bug #1288400 +++

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 8 Shyamsundar 2018-02-06 17:42:44 UTC
Thank you for your bug report.

We are no longer working on any improvements for Tier. This bug will be set to CLOSED WONTFIX to reflect this. Please reopen if the rfe is deemed critical.


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