Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Arne Jansen <sensille@gmx.net>
To: Wang Shilong <wangshilong1991@gmail.com>
Cc: "list.btrfs@jan-o-sch.net Schmidt" <list.btrfs@jan-o-sch.net>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [BUG] btrfs quota
Date: Sun, 31 Mar 2013 11:24:11 +0200	[thread overview]
Message-ID: <515800BB.50102@gmx.net> (raw)
In-Reply-To: <1DF9A68C-FBA2-460F-921F-CBF94A06CD6B@gmail.com>

Hello Wang,

On 03/31/13 03:44, Wang Shilong wrote:
> Hello Arne, Jan,
> 
>  When i run stresstest with quota enabled, i hit a panic where
> btrfs_find_all_roots() is called. Would you please double check it.
> 

On what kernel version do you hit this (git commit id preferred)?
Can you send us the message from dmesg?

Thanks,
arne

>  stresstest -n 10000  -t 4.
> 
> Maybe there is still race condition when walking backref  trees, Jan
> would you please check the backref.c ..
> btrfs_find_all_roots() is called in btrfs_qgroup_account_ref () to find
> all roots that reference a extent. I think this is called because
> 
> we introduce referenced/exclusive concepts. The point is that i think
>  this concept's disadvantages outweigh the advantages:
>       <1>
> walking backref  tree is really time-consuming.
> <2> referenced/exclusive makes it really complex when snapshot happens.
> <3> quota has a high coupling with other module.
>      I'd prefer to just keep referenced value, it is not be elegant, but
> it helps more.
> 
> Thanks,
> Wang
> 
> 
> 
> 
> 


       reply	other threads:[~2013-03-31  9:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1DF9A68C-FBA2-460F-921F-CBF94A06CD6B@gmail.com>
2013-03-31  9:24 ` Arne Jansen [this message]
2013-03-31 10:07   ` [BUG] btrfs quota Wang Shilong
2013-03-31 10:54   ` Wang Shilong

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=515800BB.50102@gmx.net \
    --to=sensille@gmx.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=list.btrfs@jan-o-sch.net \
    --cc=wangshilong1991@gmail.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