Details
-
Bug
-
Resolution: Won't Fix
-
Major
-
None
-
None
-
None
-
3
-
8408
Description
The change to enable quota by default at format time still appears to have significant metadata performance impact (25% or more), per recent testing in LU-3305.
We are now looking at whether we should disable quota by default for new filesystems, as was the case in the past Lustre releases, and we are wondering what the side effects of this will be?
It is already possible to disable quota via "tune2fs -O ^quota" after format time, and this matches the upgrade case where the quota feature is not already enabled. Is there anything beyond changing mkfs.lustre to not set the quota feature that would need to be done?
The other issue is about enabling quota on such a filesystem. For upgraded filesystems, or new filesystems that do not have quota enabled by default, this would involve "tune2fs -O quota", and then running e2fsck? Is the distributed quota state on the master automatically rebuilt at this time?
Attachments
Issue Links
- is blocking
-
-
- Resolved
-