From: Jan Kara <jack@suse.cz>
To: Carlos Carvalho <carlos@fisica.ufpr.br>
Cc: linux-ext4@vger.kernel.org
Subject: Re: 3.2.2: edquota: WARNING - /dev/md2: cannot change current block allocation
Date: Mon, 6 Feb 2012 17:10:12 +0100 [thread overview]
Message-ID: <20120206161012.GG6890@quack.suse.cz> (raw)
In-Reply-To: <20267.692.189880.355136@fisica.ufpr.br>
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@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2012-02-06 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 21:40 3.2.2: edquota: WARNING - /dev/md2: cannot change current block allocation Carlos Carvalho
2012-02-06 16:10 ` Jan Kara [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120206161012.GG6890@quack.suse.cz \
--to=jack@suse.cz \
--cc=carlos@fisica.ufpr.br \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).