xfs
[Top] [All Lists]

Re: [PATCH 0/3] xfs: change available ranges in quota check

To: Mitsuo Hayasaka <mitsuo.hayasaka.hu@xxxxxxxxxxx>
Subject: Re: [PATCH 0/3] xfs: change available ranges in quota check
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 24 Jan 2012 12:46:12 -0500
Cc: Ben Myers <bpm@xxxxxxx>, Alex Elder <aelder@xxxxxxx>, Christoph Hellwig <hch@xxxxxx>, xfs-masters@xxxxxxxxxxx, yrl.pp-manager.tt@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
In-reply-to: <20120123034513.3339.97432.stgit@xxxxxxxxxxxxxxxxxxxxxxxx>
References: <20120123034513.3339.97432.stgit@xxxxxxxxxxxxxxxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Mon, Jan 23, 2012 at 12:45:14PM +0900, Mitsuo Hayasaka wrote:
> Hi,
> 
> This patch series changes available ranges of softlimit and
> hardlimit in quota check, as follows.
> 
> (1) Consider new reservation for quota check
>     The disk block reservation checks if (current usage + new
>     reservation) reach the quota limit although the inode reservation
>     does not use the new reservation for quota check. It should
>     consider it, as well. This is mandatory for (2).

Can you send a testcase that reproduces issues with the old behaviour?

<Prev in Thread] Current Thread [Next in Thread>