From: Josef Bacik <josef@redhat.com>
To: Btrfs mailing list <linux-btrfs@vger.kernel.org>
Cc: Proskurin Kirill <k.proskurin@corp.mail.ru>
Subject: Re: [btrfs-transacti] & btrfs-endio-wri] - WAS: Re: [btrfs-delalloc-]
Date: Fri, 01 Jul 2011 10:07:39 -0400 [thread overview]
Message-ID: <4E0DD4AB.9040900@redhat.com> (raw)
In-Reply-To: <4E0D7323.9010202@corp.mail.ru>
On 07/01/2011 03:11 AM, Proskurin Kirill wrote:
> On 06/30/2011 09:13 PM, Josef Bacik wrote:
>> On 06/30/2011 10:12 AM, Proskurin Kirill wrote:
>>> On 06/29/2011 08:14 PM, Josef Bacik wrote:
>>>>> Ok - I upgrade to 2.6.39-2 but it is seems to all things get worse.
>>>>> Now I see [btrfs-transacti]& btrfs-endio-wri] 80-100% all the
> time and
>>>>> io performance looks like lower then before.
>>>>>
>>>>> Our scribe daemon in state D most of the time with half of a normal
>>>>> load. Only kernel was changed.
>>>>>
>>>>> Any performance tune recommendation?
>>>>>
>>>>
>>>> Can you get sysrq+w while this problem is happening so we can see whats
>>>> going on? Thanks,
>>>
>>> I attached sysrq+w. Hope it helps.
>>>
>>
>> Heh so it just looks like you are writing a bunch of stuff, that's not
>> particularly helpful. What does this program do generically? How full
>> is your fs? Do you have snapshots/subvolumes? If so how many? Thanks,
>
> I found what my btrfs partition now is really slow. Something wrong
> happend. I try on 2.6.32 and 2.6.39 - same result. It is because
> partition is almost full?
>
> I run a simple cycle to clean some old files:
> for i in `cat /tmp/delit`; do rm -f $i ; done
>
> And it is takes about 5-10 second per file to delete.
> I get sysrq+w while rm is work - it is attached.
>
Just a shot in the dark, but will you give this a shot and let me know
how it goes? Thanks
Josef
diff --git a/fs/btrfs/transaction.c b/fs/btrfs/transaction.c
index 654755b..698a406 100644
--- a/fs/btrfs/transaction.c
+++ b/fs/btrfs/transaction.c
@@ -475,12 +475,6 @@ static int __btrfs_end_transaction(struct
btrfs_trans_handle *trans,
trans->transaction->delayed_refs.num_heads_ready > 64) {
trans->delayed_ref_updates = 0;
- /*
- * do a full flush if the transaction is trying
- * to close
- */
- if (trans->transaction->delayed_refs.flushing)
- cur = 0;
btrfs_run_delayed_refs(trans, root, cur);
} else {
break;
next prev parent reply other threads:[~2011-07-01 14:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 7:11 [btrfs-transacti] & btrfs-endio-wri] - WAS: Re: [btrfs-delalloc-] Proskurin Kirill
2011-07-01 14:07 ` Josef Bacik [this message]
2011-07-06 16:31 ` Proskurin Kirill
-- strict thread matches above, loose matches on Subject: below --
2011-06-27 9:04 [btrfs-delalloc-] Proskurin Kirill
2011-06-27 13:21 ` [btrfs-delalloc-] Hubert Kario
2011-06-29 15:37 ` [btrfs-transacti] & btrfs-endio-wri] - WAS: [btrfs-delalloc-] Proskurin Kirill
2011-06-29 16:14 ` Josef Bacik
2011-06-30 14:12 ` Proskurin Kirill
2011-06-30 17:13 ` Josef Bacik
2011-06-30 17:19 ` Proskurin Kirill
2011-06-30 18:13 ` Proskurin Kirill
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=4E0DD4AB.9040900@redhat.com \
--to=josef@redhat.com \
--cc=k.proskurin@corp.mail.ru \
--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.