Bug 1554298 - storage.reserve limits are crossed during remove-brick operation
Summary: storage.reserve limits are crossed during remove-brick operation
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: posix
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Mohit Agrawal
QA Contact: Rahul Hinduja
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-12 11:19 UTC by Prasad Desala
Modified: 2018-03-13 05:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-13 05:29:53 UTC
Embargoed:


Attachments (Terms of Use)

Description Prasad Desala 2018-03-12 11:19:16 UTC
Description of problem:
======================
storage.reserve limits are crossed during remove-brick operation.

Version-Release number of selected component (if applicable):
3.12.2-5.el7rhgs.x86_64

How reproducible:
always

Steps to Reproduce:
===================
1) create a x3 volume and start it.
2) Set storage.reserve volume set option to 90,
gluster volume set distrepx3 storage.reserve 90
3) Create data using dd until the backend bricks reaches reserve limit.
4) Now start remove-brick operation and wait till it completes

Actual results:
===============
Though the storage reserve limits are reached, files are successfully migrated during remove-brick operation resulting in crossing the storage reserve limits.

Expected results:
================
storage.reserve limits should not be crossed during remove-brick operation.

Additional info:
================
Was able to reproduce this issue for 1MB, 5MB, 25MB file sizes.


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