Bug 1288401 - Handling char type file in the tier volume
Summary: Handling char type file in the tier volume
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: tiering
Version: 3.7.6
Hardware: All
OS: All
medium
medium
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact: bugs@gluster.org
URL:
Whiteboard:
Depends On: 1288400
Blocks: 1288403
TreeView+ depends on / blocked
 
Reported: 2015-12-04 06:26 UTC by Jiffin
Modified: 2017-03-08 10:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1288400
: 1288403 (view as bug list)
Environment:
Last Closed: 2017-03-08 10:49:21 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Jiffin 2015-12-04 06:26:26 UTC
+++ 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 1 Kaushal 2017-03-08 10:49:21 UTC
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.


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