Bug 1267464

Summary:	quota: restrict creating hard-links across quota limit directories
Product:	[Community] GlusterFS	Reporter:	Manikandan <mselvaga>
Component:	quota	Assignee:	Manikandan <mselvaga>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-bugs, mselvaga, smohan, storage-qa-internal, vagarwal, vmallika
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1265197	Environment:
Last Closed:	2015-10-07 09:05:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1265197
Bug Blocks:

Comment 1 Manikandan 2015-10-07 09:05:57 UTC

This cannot be implemented in the current quota design:
Consider below scenario

Case-1)
a) below data with hard-links pre-exists
   /d1/f1
   /d2/f1
b) Set quota limit on /d1 and /d2
c) Now when creating hard-link /d1/f1 /d1/f2 can fail
   As we do fetch the inode_parent of f1 (f1's parent can be /d1 or /d2 in the
   dentry list)

Case-2)
a) Set quota limit on /d1 and /d2
b) create file /d1/f1 and link /d1/f2
c) rename /d1/f2 /d2/f2
d) Now when creating hard-link /d1/f1 /d1/f2 can fail
   As we do fetch the inode_parent of f1 (f1's parent can be /d1 or /d2 in the
   dentry list)


So marking the bug as wontfix