Bug 762742 (GLUSTER-1010)

Summary: We can use 1 drive associated with 2 different volumes
Product: [Retired] GlusterSP Reporter: it_admin
Component: coreAssignee: Balamurugan Arumugam <bala>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 3.0.4CC: platform, shireesh
Target Milestone: 3.1   
Target Release: ---   
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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!