Skip to contentSkip to conversation

- Bug 675944 - gfs2 quota allows exceeding hard limit

PATCH New Abhijith Das 2 participants 2 messages Mar 8, 2011 – Mar 9, 2011 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): 2128286308.330630.1299598759037.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com

#1 lore raw

PATCH 1/1 - Bug 675944 - gfs2 quota allows exceeding hard limit

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: bz675944-upstream.patch
Type: text/x-patch
Size: 1240 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20110308/56ab5a45/attachment.bin>

#2 lore raw

PATCH 1/1 - Bug 675944 - gfs2 quota allows exceeding hard limit

Hi,

Quoted 6 lines · Abhijith Das

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

Now in the -nmw git tree. Thanks,

Steve.