From: Miao Xie <miaox@cn.fujitsu.com>
To: Itaru Kitayama <kitayama@cl.bb4u.ne.jp>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH V3] btrfs: implement delayed inode items operation
Date: Fri, 18 Mar 2011 17:18:13 +0800 [thread overview]
Message-ID: <4D832355.70200@cn.fujitsu.com> (raw)
In-Reply-To: <20110318175904.4e983b7f.kitayama@cl.bb4u.ne.jp>
On fri, 18 Mar 2011 17:59:04 +0900, Itaru Kitayama wrote:
> Hi Miao,
>
> Your updated V4 patch no longer gives me a hang. Thank you.
>
> In the latest V4, btrfs_remove_delayed_node() does just release
> a delayed node and returns for most of the time, but for space
Right.
> cache inodes, it takes trans_mutex and writes the delayed nodes
> out to the tree. Is my understanding correct?
for space cache inodes, we just update them in time, don't delayed to
update them.
Thanks
Miao
>
> On Fri, 18 Mar 2011 11:37:03 +0800
> Miao Xie <miaox@cn.fujitsu.com> wrote:
>
>> I find the inodes of free space information are updated when committing transaction,
>> and it will lead btrfs to hang.
>>
>> I have fixed this bug in the attached patch, could you test for me? I have tested it
>> on my machine with space_cache mount option, it worked well.
>>
>> Thanks
>> Miao
> --
> 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
>
next prev parent reply other threads:[~2011-03-18 9:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 15:03 [PATCH V3] btrfs: implement delayed inode items operation Itaru Kitayama
2011-03-10 6:21 ` Miao Xie
2011-03-16 9:48 ` Itaru Kitayama
2011-03-16 14:24 ` Miao Xie
2011-03-16 17:49 ` Chris Mason
2011-03-17 1:37 ` Itaru Kitayama
2011-03-18 3:37 ` Miao Xie
2011-03-18 8:59 ` Itaru Kitayama
2011-03-18 9:18 ` Miao Xie [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-03 6:06 Miao Xie
2011-03-05 7:01 ` Itaru Kitayama
2011-03-06 23:25 ` Tsutomu Itoh
2011-03-07 1:57 ` Miao Xie
2011-03-10 3:07 ` Itaru Kitayama
2011-03-08 16:56 ` David Sterba
2011-03-09 5:40 ` Miao Xie
2011-03-11 15:24 ` David Sterba
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=4D832355.70200@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=kitayama@cl.bb4u.ne.jp \
--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;
as well as URLs for NNTP newsgroup(s).