Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Khaled Ahmed <khaled.gnu@gmail.com>
To: Dongsheng Yang <dongsheng081251@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Fixing quota error when removing files from a limit exceeded subvols
Date: Sat, 3 Jan 2015 16:29:36 +0200	[thread overview]
Message-ID: <2DAD7296-8CD0-4733-9CED-FF06397B3C99@gmail.com> (raw)
In-Reply-To: <CA+qeAOqzm14gGx4R5Bc-+hZkyRmTPq_jST+Ke0AyszSD0inHZg@mail.gmail.com>

Hi Yang,

This is how to reproduce the bug,

[root@algodev ~]# uname -r
3.18.0+

[root@algodev ~]# btrfs version
Btrfs v3.18-2-g6938452-dirty

[root@algodev ~]# btrfs quota enable LOOP/
[root@algodev ~]# btrfs qgroup show  LOOP/
qgroupid rfer  excl  
-------- ----  ----  
0/5      16384 16384 

[root@algodev ~]# btrfs subvol create LOOP/subvol1
Create subvolume 'LOOP/subvol1'

[root@algodev ~]# btrfs qgroup limit 1g LOOP/subvol1/

[root@algodev ~]# btrfs qgroup show  LOOP/
qgroupid rfer  excl  
-------- ----  ----  
0/5      16384 16384 
0/258    16384 16384 

[root@algodev ~]# dd if=/dev/zero of=LOOP/subvol1/bigfile
dd: writing to ‘LOOP/subvol1/bigfile’: Disk quota exceeded
2097018+0 records in
2097017+0 records out
1073672704 bytes (1.1 GB) copied, 10.0759 s, 107 MB/s

[root@algodev ~]# rm -f LOOP/subvol1/bigfile 
rm: cannot remove ‘LOOP/subvol1/bigfile’: Disk quota exceeded
[root@algodev ~]# 

Best Regards,
~Khaled Ahmed


On Jan 3, 2015, at 4:09 AM, Dongsheng Yang <dongsheng081251@gmail.com> wrote:

> Hi Khaled,
> 
> Could you give use more description about the problem this patch
> is trying to solve? Maybe an example will help a lot to understand it.
> 
> Thanx
> 
> On Fri, Jan 2, 2015 at 7:48 AM, Khaled Ahmed <khaled.gnu@gmail.com> wrote:
>> Signed-off-by: Khaled Ahmed <khaled.gnu@gmail.com>
>> ---
>> fs/btrfs/qgroup.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>> 
>> diff --git a/fs/btrfs/qgroup.c b/fs/btrfs/qgroup.c
>> index 48b60db..b85200d 100644
>> --- a/fs/btrfs/qgroup.c
>> +++ b/fs/btrfs/qgroup.c
>> @@ -2408,14 +2408,14 @@ int btrfs_qgroup_reserve(struct btrfs_root *root, u64 num_bytes)
>> 
>>                if ((qg->lim_flags & BTRFS_QGROUP_LIMIT_MAX_RFER) &&
>>                    qg->reserved + (s64)qg->rfer + num_bytes >
>> -                   qg->max_rfer) {
>> +                   qg->max_rfer - 1 ) {
>>                        ret = -EDQUOT;
>>                        goto out;
>>                }
>> 
>>                if ((qg->lim_flags & BTRFS_QGROUP_LIMIT_MAX_EXCL) &&
>>                    qg->reserved + (s64)qg->excl + num_bytes >
>> -                   qg->max_excl) {
>> +                   qg->max_excl - 1) {
>>                        ret = -EDQUOT;
>>                        goto out;
>>                }
>> --
>> 2.1.0
>> 
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2015-01-03 14:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-01 23:48 [PATCH] Fixing quota error when removing files from a limit exceeded subvols Khaled Ahmed
2015-01-03  2:09 ` Dongsheng Yang
2015-01-03 14:29   ` Khaled Ahmed [this message]
2015-01-04 10:54     ` Dongsheng Yang

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=2DAD7296-8CD0-4733-9CED-FF06397B3C99@gmail.com \
    --to=khaled.gnu@gmail.com \
    --cc=dongsheng081251@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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