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: <20130131222817.GB13525@quack.suse.cz>
Date:	Thu, 31 Jan 2013 23:28:17 +0100
From:	Jan Kara <jack@...e.cz>
To:	Theodore Ts'o <tytso@....edu>
Cc:	Carlos Carvalho <carlos@...ica.ufpr.br>,
	Aditya Kali <adityakali@...gle.com>,
	ext4 development <linux-ext4@...r.kernel.org>,
	Jan Kara <jack@...e.cz>
Subject: Re: how to quotacheck with the new quota implementation (hidden
 inode)?

On Thu 31-01-13 17:03:12, Ted Tso wrote:
> On Thu, Jan 31, 2013 at 05:13:16PM -0200, Carlos Carvalho wrote:
> > 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.
> 
> This sequence documents the biggest set of issues with the new
> implementation:
> 
> 1) Create a file system.  Populate it with files.  I untarred the
> e2fsprogs source tree as root, so there were a lot of files owned by
> root.
> 
> 2)  unmount the filesystem and run tune2fs -O quota /dev/XXX
> 
> 3) mount the file system; observe that the quota tools don't realize
> that they should be trying to do the quota thing.
  What version of quota-tools are you using? If I didn't screw up
something, version 4.01 shouldn't need the -o quota mount option anymore...

								Honza
-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
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

Powered by blists - more mailing lists