linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Proskurin Kirill <k.proskurin@corp.mail.ru>
To: Josef Bacik <josef@redhat.com>
Cc: Btrfs mailing list <linux-btrfs@vger.kernel.org>
Subject: Re: [btrfs-transacti] & btrfs-endio-wri] - WAS: Re: [btrfs-delalloc-]
Date: Wed, 06 Jul 2011 20:31:32 +0400	[thread overview]
Message-ID: <4E148DE4.7070904@corp.mail.ru> (raw)
In-Reply-To: <4E0DD4AB.9040900@redhat.com>

On 07/01/2011 06:07 PM, Josef Bacik wrote:

>> 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

Sorry for late answer. Im afraid I can`t test it now - then problem 
occurs I have no time to wait and format partition. But I will save 
this patch and if I run at this problem again I will try it and report 
here.

Thanks for your help anyway.

-- 
Best regards,
Proskurin Kirill

  reply	other threads:[~2011-07-06 16:31 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
2011-07-06 16:31   ` Proskurin Kirill [this message]
  -- 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=4E148DE4.7070904@corp.mail.ru \
    --to=k.proskurin@corp.mail.ru \
    --cc=josef@redhat.com \
    --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).