From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] - Bug 675944 - gfs2 quota allows exceeding hard limit
Date: Wed, 09 Mar 2011 09:58:11 +0000 [thread overview]
Message-ID: <1299664691.2587.0.camel@dolmen> (raw)
In-Reply-To: <956492768.330676.1299598842750.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
Hi,
On Tue, 2011-03-08 at 10:40 -0500, Abhijith Das wrote:
> Immediately after being synced to disk, cached quotas are zeroed out and a subsequent access of the cached quotas results in incorrect zero values. This meant that gfs2 assumed the actual usage to be the zero (or near-zero) usage values it found in the cached quotas and comparison against warn/limits never triggered a quota violation.
>
> This patch adds a new flag QDF_REFRESH that is set after a sync so that the cached quotas are forcefully refreshed from disk on a subsequent access on seeing this flag set.
>
> Resolves: rhbz#675944
> Signed-off-by: Abhi Das <adas@redhat.com>
Now in the -nmw git tree. Thanks,
Steve.
prev parent reply other threads:[~2011-03-09 9:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2128286308.330630.1299598759037.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2011-03-08 15:40 ` [Cluster-devel] [GFS2 PATCH] - Bug 675944 - gfs2 quota allows exceeding hard limit Abhijith Das
2011-03-09 9:58 ` Steven Whitehouse [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=1299664691.2587.0.camel@dolmen \
--to=swhiteho@redhat.com \
/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).