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?
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 <[email protected]>
SUSE Labs, CR