All of lore.kernel.org
 help / color / mirror / Atom feed
From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
	Kevin Brandstatter <icarusthecow@gmail.com>
Subject: [BUG] "Quota Ignored On write" problem still exist with 3.16-rc5
Date: Fri, 18 Jul 2014 17:45:36 +0900	[thread overview]
Message-ID: <53C8DEB0.1060404@jp.fujitsu.com> (raw)

Hi Josef, Chris,

I found "Quota Ignored On write" problem still exist with 3.16-rc5,
which Kevin reported before.

Kevin's report:
https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg35292.html

The result of bisect:
https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg35304.html

> I bisected and found the bad commit is the following patch.
> 
> ===============================================================================
> commit fcebe4562dec83b3f8d3088d77584727b09130b2
> Author: Josef Bacik <jba...@fb.com>
> Date:   Tue May 13 17:30:47 2014 -0700
> 
>     Btrfs: rework qgroup accounting
> ===============================================================================
> 
> Josef, please take a look at this patch.

Reproducer:
https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg35299.html

Could you tell me the progress of fixing this bug?
In addition, could you fix it by 3.16?

command log:
===============================================================================
# ./test.sh
+ uname -a
Linux luna.soft.fujitsu.com 3.16.0-rc5 #2 SMP Tue Jul 15 13:39:46 JST 2014 x86_64 x86_64 x86_64 GNU/Linux
+ df -T /test7
Filesystem     Type  1K-blocks  Used Available Use% Mounted on
/dev/sdc7      btrfs  29296640  1536  27169536   1% /test7
+ btrfs quota ena /test7
+ cd /test7
+ btrfs sub cre test
Create subvolume './test'
+ btrfs sub l -a /test7
ID 270 gen 66 top level 5 path test
+ btrfs qg lim 1G test                          # limit test subvol to 1GB
+ btrfs qg show -pcre /test7
qgroupid rfer  excl  max_rfer   max_excl parent  child
-------- ----  ----  --------   -------- ------  -----
0/5      16384 16384 0          0        ---     ---
0/270    16384 16384 1073741824 0        ---     ---
+ dd if=/dev/zero of=test/file0 bs=1M count=2000
2000+0 records in
2000+0 records out
2097152000 bytes (2.1 GB) copied, 9.67876 s, 217 MB/s   # write 2GB. It's a bug!
+ sync
+ ls -lisaR /test7
/test7:
total 20
256 16 drwxr-xr-x   1 root root    8 Jul 18 15:12 .
  2  4 drwxr-xr-x. 43 root root 4096 Jul 16 08:34 ..
256  0 drwxr-xr-x   1 root root   10 Jul 18 15:17 test

/test7/test:
total 2048016
256       0 drwxr-xr-x 1 root root         10 Jul 18 15:17 .
256      16 drwxr-xr-x 1 root root          8 Jul 18 15:12 ..
257 2048000 -rw-r--r-- 1 root root 2097152000 Jul 18 15:17 file0
+ btrfs qg show -pcre /test7
qgroupid rfer       excl       max_rfer   max_excl parent  child
-------- ----       ----       --------   -------- ------  -----
0/5      16384      16384      0          0        ---     ---
0/270    2097168384 2097168384 1073741824 0        ---     ---
+ btrfs quota dis /test7
+ btrfs sub del test
Transaction commit: none (default)
Delete subvolume '/test7/test'
+ set +x
#
===============================================================================

  NOTE:
  The reproducer here (./test.sh) is a bit different from above-mentioned
  one because of some reason.

Thanks,
Satoru


             reply	other threads:[~2014-07-18  8:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18  8:45 Satoru Takeuchi [this message]
2014-07-18 10:29 ` [BUG] "Quota Ignored On write" problem still exist with 3.16-rc5 Wang Shilong
2014-07-23  0:53   ` Satoru Takeuchi
2014-07-23  1:54     ` Wang Shilong
2014-07-23 13:23     ` Josef Bacik
2014-07-24 22:51       ` Kevin Brandstatter

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=53C8DEB0.1060404@jp.fujitsu.com \
    --to=takeuchi_satoru@jp.fujitsu.com \
    --cc=clm@fb.com \
    --cc=icarusthecow@gmail.com \
    --cc=jbacik@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.