Hide Forgot
2- What is the nature and description of the request? This customer uses a quota-managed FS over samba and wants to have samba delete files automatically after they have not been accessed for some time, based on the atime value. 3- Why does the customer need this? (List the business requirements here) The problem is that quotacheck changes the atime for all the files when it's being used, causing the cleanup never to work. 4- How would the customer like to achieve this? (List the functional requirements here) The customer wants us to add an option to quotacheck that will cause it not to change the atime on the files, making it so that the customer can use samba to base itself on that time to decide which files have to be removed. 5- For each functional requirement listed in question 4, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Running ls -l, then quotacheck, then ls -l on a quota-enabled fs should show that the atimes for the files have not changed when using the said option 6- Is there already an existing RFE upstream or in Red Hat bugzilla? No BZ exist at this time, and there is no such option of Quotacheck at the present time. 7- How quickly does this need resolved? (desired target release) RHEL5.7 8- Does this request meet the RHEL Inclusion criteria (please review) Yes 9- List the affected packages quota 10- Would the customer be able to assist in testing this functionality if implemented? yes
I cannot reproduce it. quotacheck handles ext3 and ext4 differently. E.g. in case of ext4 with vsfv0 quota format it opens each file to get file descriptor to pass it to FIOQSIZE ioctl() to the get space occupied by the file including metadata (i-node). However it never accesses content of the file (read() system call), thus it should not update access time of the file. Which file system customer does use and how does he mount it? Corresponding line from /proc/mount would be helpful.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Closing this request because of lack of details how to reproduce this problem.