This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 1267464 - quota: restrict creating hard-links across quota limit directories
quota: restrict creating hard-links across quota limit directories
Status: CLOSED WONTFIX
Product: GlusterFS
Classification: Community
Component: quota (Show other bugs)
mainline
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Manikandan
: ZStream
Depends On: 1265197
Blocks:
  Show dependency treegraph
 
Reported: 2015-09-30 02:40 EDT by Manikandan
Modified: 2016-09-20 00:28 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1265197
Environment:
Last Closed: 2015-10-07 05:05:57 EDT
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)
Comment 1 Manikandan 2015-10-07 05:05:57 EDT
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

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