On 2014-04-02 11:43, Michael Meskes wrote: > On Mon, Mar 31, 2014 at 02:25:20PM +1100, Matthew Cengia wrote: > > Even when using journalled quotas on a filesystem which has had > > quotacheck run on it manually to ensure it is accurate, quotacheck still > > gets run on boot when 'quota' is started by init. This is unnecessary > > and adds 30 minutes to my system's boot time. > > I don't really understand what you're saying here. If the quota system is shut > down correctly there should be no quotacheck run during boot. Are you saying > you still get one?
Hi Michael, Thanks for your response. The documentation at /usr/share/doc/quota/quotadoc.sgml.gz indicates that quotacheck isn't required to be run at all (except when quotas are first configured) when using journalled quotas (i.e. the usrjquota mount option). It doesn't say that it needs to be run, but will do nothing if the filesystem was unmounted cleanly. I understand from this that running quotacheck on a filesystem with a journalled quota does unnecessary work, and does nothing more than slow the boot. You're right that when the filesystem is unmounted cleanly during shutdown, quotacheck doesn't do a full scan of the filesystem on boot, but does do it when the filesystem is not unmounted cleanly (e.g. a hard reset rather than graceful shutdown). It sounds like the latter isn't necessary. Is this correct? If so, then there should be logic in /etc/init.d/quota to check whether the filesystem's mount options include usrjquota/grpjquota and *not* usrquota/grpquota, and if this is the case, refrain from invoking quotacheck. If my understanding is incorrect, I'd love for you to explain to me how this all works. -- Regards, Matthew Cengia
signature.asc
Description: Digital signature
