Bug 1288403 - Handling char type file in the tier volume
Handling char type file in the tier volume
Status: NEW
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: tier (Show other bugs)
3.1
All All
medium Severity medium
: ---
: ---
Assigned To: Dan Lambright
nchilaka
: Triaged, ZStream
Depends On: 1288400 1288401
Blocks: 1286022
  Show dependency treegraph
 
Reported: 2015-12-04 01:28 EST by Jiffin
Modified: 2017-06-28 05:08 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1288401
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jiffin 2015-12-04 01:28:19 EST
+++ 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:

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