From: Abhijith Das <adas@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2][PATCH] - Allow gfs2 to update quota usage values through the quotactl interface [REPOST]
Date: Thu, 18 Nov 2010 11:26:46 -0500 (EST) [thread overview]
Message-ID: <932110648.2701541290097606317.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <1900460402.2701411290097563356.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
With this patch the gfs2_set_dqblk() function will be able to update the quota usage block count (FS_DQ_BCOUNT) in addition to the already supported FS_DQ_BHARD (limit) and FS_DQ_BSOFT (warn) fields of the dquot structure.
Signed-off-by: Abhi Das <adas@redhat.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bz696794-upstream-gfs2-allow-update-of-quota-usage.patch
Type: text/x-patch
Size: 1567 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20101118/72cc3051/attachment.bin>
parent reply other threads:[~2010-11-18 16:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1900460402.2701411290097563356.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>]
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=932110648.2701541290097606317.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com \
--to=adas@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).