linux-ext4 - Re: 3.2.2: edquota: WARNING - /dev/md2: cannot change current block allocation

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] [day] [month] [year] [list]

Date:	Mon, 6 Feb 2012 17:10:12 +0100
From:	Jan Kara <jack@...e.cz>
To:	Carlos Carvalho <carlos@...ica.ufpr.br>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: 3.2.2: edquota: WARNING - /dev/md2: cannot change current
 block allocation

On Thu 02-02-12 19:40:04, Carlos Carvalho wrote:
> When I tried to increase the quota of a user (postgres) I got this
> edquota warning. The output of quota still showed the * indicating the
> limit and the user couldn't allocate more disk. After a reboot (to
> 3.2.1) and quotacheck I had to use edquota again, and then it accepted
> the increase and unblocked the allocations.
> 
> This is the output of mount|grep /dev/md2:
> /dev/md2 on /home type ext4 (rw,relatime,user_xattr,acl,barrier=0,stripe=128,data=ordered,inode_readahead_blks=64,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)
> 
> How can this be?
  Well, the message suggests that you edited actual block usage of user and
not his limit. That's why edquota complained and didn't change anything...
So it's nothing related to kernel nor a bug ;).

  As a side note, I always found edquota(8) error prone and I think
setquota(8) is a better tool to do what I need. But I guess it depends on
one's taste.

								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