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: Thu, 30 Jun 2011 13:13:02 -0400 [thread overview]
Message-ID: <4E0CAE9E.7000406@redhat.com> (raw)
In-Reply-To: <4E0C8443.7070109@corp.mail.ru>
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,
Josef
next prev parent reply other threads:[~2011-06-30 17:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2011-06-30 17:19 ` Proskurin Kirill
2011-06-30 18:13 ` Proskurin Kirill
-- strict thread matches above, loose matches on Subject: below --
2011-07-01 7:11 Proskurin Kirill
2011-07-01 14:07 ` Josef Bacik
2011-07-06 16:31 ` 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=4E0CAE9E.7000406@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 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).