Bug 762742 (GLUSTER-1010) - We can use 1 drive associated with 2 different volumes
Summary: We can use 1 drive associated with 2 different volumes
Keywords:
Status: CLOSED NOTABUG
Alias: GLUSTER-1010
Product: GlusterSP
Classification: Retired
Component: core
Version: 3.0.4
Hardware: x86_64
OS: All
low
medium
Target Milestone: 3.1
Assignee: Balamurugan Arumugam
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-18 15:01 UTC by it_admin
Modified: 2010-11-29 10:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Balamurugan Arumugam 2010-06-18 12:33:46 UTC 
As volumes are thin provisioned, this is expected behavior.
Comment 1 it_admin 2010-06-18 15:01:38 UTC 
When we create a volume, you have the possibility to use the same drive for multiple volumes, which is not a good thing. For example, you can create volume1 with drive1, and you can create volume2 with drive1... We ran some test with 1 drive associated in 2 different volumes and here's what's the results. On volume1, you can't see the files from volume2 and vice-versa, but, if you use all the space on volume1, volume2 won't be able to receive anything, since volume1 is full. 

Any ideas if this bug was already known by any other users? Will it be fixed in next patch?

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