linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: 3.19-rc5: Bug 91911: [REGRESSION] rm command hangs big time with deleting a lot of files at once
Date: Fri, 23 Jan 2015 09:56:54 -0500	[thread overview]
Message-ID: <1422025014.28436.1@mail.thefacebook.com> (raw)
In-Reply-To: <pan.2015.01.23.14.38.09@googlemail.com>



On Fri, Jan 23, 2015 at 9:38 AM, Holger Hoffstätte 
<holger.hoffstaette@googlemail.com> wrote:
> On Fri, 23 Jan 2015 15:01:28 +0100, Martin Steigerwald wrote:
> 
>>  Hi!
>> 
>>  Anyone seen this?
>> 
>>  Reported as:
>> 
>>  
>> https://urldefense.proofpoint.com/v1/url?u=https://bugzilla.kernel.org/show_bug.cgi?id%3D91911&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=6%2FL0lzzDhu0Y1hL9xm%2BQyA%3D%3D%0A&m=fHpzX%2FNpDGcY26Q1T%2B0VtIyZz0GPMnG3qvE%2FVJ%2Blsf0%3D%0A&s=66b06542cc5a9585c9913a0b76885b4baba0a8028f70149803982388c9333d71
> 
> You might be interested in:
> 
> https://urldefense.proofpoint.com/v1/url?u=https://git.kernel.org/cgit/linux/kernel/git/josef/btrfs-next.git/commit/?h%3Devict-softlockup%26id%3D29249e14d6e3379a5c4bb098dd4beddfefbc606f&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=6%2FL0lzzDhu0Y1hL9xm%2BQyA%3D%3D%0A&m=fHpzX%2FNpDGcY26Q1T%2B0VtIyZz0GPMnG3qvE%2FVJ%2Blsf0%3D%0A&s=137b101ca50e644b95dc2b14758cf1472e9cc0097b4f89f7edf8e2845455b20f
> 
> and
> 
> https://urldefense.proofpoint.com/v1/url?u=https://git.kernel.org/cgit/linux/kernel/git/josef/btrfs-next.git/commit/?h%3Devict-softlockup%26id%3De4a58b71ff981b098ac3371f4d573dc6a90006ce&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=6%2FL0lzzDhu0Y1hL9xm%2BQyA%3D%3D%0A&m=fHpzX%2FNpDGcY26Q1T%2B0VtIyZz0GPMnG3qvE%2FVJ%2Blsf0%3D%0A&s=3462ceb04ffed8316e21ffe16eee4e3274f9771a58326cd1bbb9c1cfc1eef9ba
> 
> I'm sure everyone would love to hear how this works out for you ;-)

These are a little different.  Josef is fixing softlockups (CPUs pegged 
in R state) while this bug report is for sleeping procs.  The fact that 
things come back sound like we're pegged waiting for IO?  Do you have a 
lot of writing going on at the same time?

-chris




  reply	other threads:[~2015-01-23 14:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 14:01 3.19-rc5: Bug 91911: [REGRESSION] rm command hangs big time with deleting a lot of files at once Martin Steigerwald
2015-01-23 14:38 ` Holger Hoffstätte
2015-01-23 14:56   ` Chris Mason [this message]
2015-01-24 14:14     ` Martin Steigerwald
2015-01-26  4:42   ` Zygo Blaxell
2015-01-23 23:29 ` Zygo Blaxell
2015-01-24 10:20   ` Martin Steigerwald
2015-01-25 22:14   ` Zygo Blaxell

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=1422025014.28436.1@mail.thefacebook.com \
    --to=clm@fb.com \
    --cc=holger.hoffstaette@googlemail.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).