linux-ext4 - Re: how to quotacheck with the new quota implementation (hidden inode)?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20746.49740.638811.698394@fisica.ufpr.br>
Date:	Thu, 31 Jan 2013 17:13:16 -0200
From:	Carlos Carvalho <carlos@...ica.ufpr.br>
To:	Aditya Kali <adityakali@...gle.com>
Cc:	"Theodore Ts'o" <tytso@....edu>,
	ext4 development <linux-ext4@...r.kernel.org>,
	Jan Kara <jack@...e.cz>
Subject: Re: how to quotacheck with the new quota implementation (hidden inode)?

Aditya Kali (adityakali@...gle.com) wrote on 31 January 2013 11:04:
 >By default, only usage is enabled when the filesystem is mounted. You
 >will need to call quotaon to turn on limit enforcement. If it doesn't
 >even after that, then its a bug.

Ah, fine. It works, fortunately :-). Thanks.

It's not clear what can be dropped and what must still be used in the
new implementation. It'd be nice to state it in the man page of
tune2fs, for example. I thought that if we wanted to stop quotas it'd
be necessary to umount and tune2fs again.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html