From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 15074] Problem with quota on ext4
Date: Wed, 10 Feb 2010 08:50:34 GMT [thread overview]
Message-ID: <201002100850.o1A8oY11017405@demeter.kernel.org> (raw)
In-Reply-To: <bug-15074-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=15074
--- Comment #12 from Dmitri Monakhov <dmonakhov@openvz.org> 2010-02-10 08:49:56 ---
Created an attachment (id=24986)
--> (http://bugzilla.kernel.org/attachment.cgi?id=24986)
print warning about inconsistent quota usage
Jan this patch does as much as we can in case of unexpected quota
inconsistency.
I should be applied on top of
http://marc.info/?l=linux-ext4&m=126106356824375&w=2
Should i combine it in to one patch ?
1) It charge reserved space during quotaon
2) fixup quota_reservation on claim and release.
In both cases error message will be printed(in first case it will be printed
twice)
test
dd if=/dev/zero of=/mnt bs=1k &
quotaon /mnt
killall dd
sync
I've test it and has got nice warning messages without triggering WARN(true)
in claim_rsv and free_rsv
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2010-02-10 8:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 21:49 [Bug 15074] New: Problem with quota on ext4 bugzilla-daemon
2010-01-29 17:28 ` [Bug 15074] " bugzilla-daemon
2010-02-02 17:49 ` bugzilla-daemon
2010-02-09 14:41 ` bugzilla-daemon
2010-02-09 15:10 ` bugzilla-daemon
2010-02-09 16:02 ` bugzilla-daemon
2010-02-09 16:36 ` bugzilla-daemon
2010-02-09 16:57 ` bugzilla-daemon
2010-02-09 17:25 ` bugzilla-daemon
2010-02-09 17:27 ` bugzilla-daemon
2010-02-10 6:18 ` bugzilla-daemon
2010-02-10 6:38 ` bugzilla-daemon
2010-02-10 8:50 ` bugzilla-daemon [this message]
2010-02-10 19:01 ` bugzilla-daemon
2010-02-10 19:17 ` bugzilla-daemon
2010-02-15 14:20 ` bugzilla-daemon
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=201002100850.o1A8oY11017405@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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).