From: Christoph Hellwig <hch@infradead.org>
To: "Guk-Bong, Kwon" <gbkwon@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: [help] project quota information incorrect over nfs ...
Date: Thu, 21 Jan 2010 06:17:20 -0500 [thread overview]
Message-ID: <20100121111720.GA20641@infradead.org> (raw)
In-Reply-To: <77cc6e171001202012y9472a42m849bcea8910ca290@mail.gmail.com>
On Thu, Jan 21, 2010 at 01:12:06PM +0900, Guk-Bong, Kwon wrote:
> nfs client "nfs_server:/test/111" Size is correct..(100M)
>
> but nfs client "nfs_server:/test/111" Avail is incorrect.. (500M)
>
> "Avail" is big than "Size" ...
>
> this stat is normal??
No, it's not. The patch below should fix it, but I'm not sure how
easily backportable it is to 2.6.27:
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: linux-2.6/fs/xfs/quota/xfs_qm_bhv.c
===================================================================
--- linux-2.6.orig/fs/xfs/quota/xfs_qm_bhv.c 2010-01-21 12:13:51.397003969 +0100
+++ linux-2.6/fs/xfs/quota/xfs_qm_bhv.c 2010-01-21 12:14:14.290009571 +0100
@@ -59,7 +59,7 @@ xfs_fill_statvfs_from_dquot(
be64_to_cpu(dp->d_blk_hardlimit);
if (limit && statp->f_blocks > limit) {
statp->f_blocks = limit;
- statp->f_bfree =
+ statp->f_bfree = statp->f_bavail =
(statp->f_blocks > be64_to_cpu(dp->d_bcount)) ?
(statp->f_blocks - be64_to_cpu(dp->d_bcount)) : 0;
}
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-01-21 11:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 4:12 [help] project quota information incorrect over nfs Guk-Bong, Kwon
2010-01-21 11:17 ` Christoph Hellwig [this message]
2010-01-21 21:55 ` Alex Elder
2010-01-22 9:54 ` Guk-Bong, Kwon
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=20100121111720.GA20641@infradead.org \
--to=hch@infradead.org \
--cc=gbkwon@gmail.com \
--cc=xfs@oss.sgi.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