From: Proskurin Kirill <k.proskurin@corp.mail.ru>
To: Hubert Kario <hka@qbs.com.pl>
Cc: Btrfs mailing list <linux-btrfs@vger.kernel.org>
Subject: [btrfs-transacti] & btrfs-endio-wri] - WAS: Re: [btrfs-delalloc-]
Date: Wed, 29 Jun 2011 19:37:46 +0400 [thread overview]
Message-ID: <4E0B46CA.2030205@corp.mail.ru> (raw)
In-Reply-To: <201106271521.54497.hka@qbs.com.pl>
On 06/27/2011 05:21 PM, Hubert Kario wrote:
> On Monday 27 of June 2011 11:04:06 Proskurin Kirill wrote:
>> Hello all.
>>
>> What we have:
>> SL6 - kernel 2.6.32-131.2.1.el6.x86_64
>> btrfs on mdadm RAID5 with 8 HDD - 27T partition.
>>
>> I see this at top:
>> 1182 root 20 0 0 0 0 R 100.0 0.0 16:39.73
>> [btrfs-delalloc-]
>>
>> And LA is grow. What is this and how can I fix it?
>
> delalloc is a delayed allocation kernel thread -- it probably means something
> is writing large amounts of data to the file system
>
> 2.6.32 is *old* as far as btrfs is concerned, there have been many bugs fixed
> and performance improvements since
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?
--
Best regards,
Proskurin Kirill
next prev parent reply other threads:[~2011-06-29 15:37 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 ` Proskurin Kirill [this message]
2011-06-29 16:14 ` [btrfs-transacti] & btrfs-endio-wri] - WAS: [btrfs-delalloc-] 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
-- 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=4E0B46CA.2030205@corp.mail.ru \
--to=k.proskurin@corp.mail.ru \
--cc=hka@qbs.com.pl \
--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.