From: Jeroen Massar <jeroen@unfix.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: CPU stuck for 67s (kernel BUG) + in xfs_trans_committed_bulk while deleting lots a files (mostly hard-links)
Date: Wed, 07 Sep 2011 17:48:12 +0200 [thread overview]
Message-ID: <4E67923C.80204@unfix.org> (raw)
In-Reply-To: <20110907113723.GA1701@infradead.org>
On 2011-09-07 13:37 , Christoph Hellwig wrote:
> On Wed, Sep 07, 2011 at 01:04:54PM +0200, Jeroen Massar wrote:
>> As partially mentioned in the kernel BUG message this is Debian's
>> edition of linux-image-2.6.39-2-amd64 and according to the Debian
>> changelogs nothing new has been introduced. 3.0.0-3 is available, but as
>> kernel.org is down, bit hard to figure out what changes where made
>> between those versions and if they can affect this at all...
>>
>> Anybody any ideas? :)
>
> You'll want at least commit 1316d4da3f632d5843d5a446203e73067dc40f09
>
> xfs: unpin stale inodes directly in IOP_COMMITTED
>
> from kernel 3.0. In addition commit 1d8c95a363bf8cd4d4182dd19c01693b635311c2
>
> xfs: use a cursor for bulk AIL insertion
>
> from 3.1-rc should help even more with this workload.
Upgraded to the 3.1-rc4 from experimental, and all seems to be quite
fine upto now. Even with 60% system during rm's it is not freezing up
(upto now, that I noticed) thus that is a great thing.
Thanks for getting this problem out of the way.
Greets,
Jeroen
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-09-07 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 11:04 CPU stuck for 67s (kernel BUG) + in xfs_trans_committed_bulk while deleting lots a files (mostly hard-links) Jeroen Massar
2011-09-07 11:37 ` Christoph Hellwig
2011-09-07 15:48 ` Jeroen Massar [this message]
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=4E67923C.80204@unfix.org \
--to=jeroen@unfix.org \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.com \
/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