mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: 2.6.38.1: CPU#0 stuck for 67s! / xfs_ail_splice
Date: Mon, 28 Mar 2011 04:10:11 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1103280406300.25113@p34.internal.lan> (raw)
In-Reply-To: <20110327232543.GU26611@dastard>



On Mon, 28 Mar 2011, Dave Chinner wrote:

> On Sat, Mar 26, 2011 at 09:29:36AM -0400, Justin Piszcz wrote:
>> Hi,
>>
>> When I rm -rf a directory of a few hundred thousand
>> files/directories on XFS under 2.6.38.1, I see the following, is
>> this normal?
>
> No. What is you filesystem config (xfs_info) and your mount options?
> Is it repeatable? I? the system otherwise stalled or is it still
> operating normally? Does it recover and work normally after such a
> stall?

Hi Dave, default mkfs.xfs options:

> What is you filesystem config (xfs_info) and your mount options?

# xfs_info /dev/sda1
meta-data=/dev/sda1              isize=256    agcount=44, agsize=268435455 blks
          =                       sectsz=512   attr=2
data     =                       bsize=4096   blocks=11718704640, imaxpct=5
          =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0
log      =internal               bsize=4096   blocks=521728, version=2
          =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0

/dev/sda1 on /r1 type xfs (rw,noatime,nobarrier,logbufs=8,logbsize=262144,delaylog,inode64)

> Is it repeatable?
I've not tried to repeat it as is spews messages over all of my consoles but
it has happened more than once.

> the system otherwise stalled or is it still operating normally?
The console/xterm/ssh etc that is performing the removal does lockup but
you are able to access the machine via a separate ssh connection.

> Does it recover and work normally after such a stall?
Yes, eventually, I believe I started seeing this problem when I added
'delaylog' option to the mount options..

Justin.


  reply	other threads:[~2011-03-28  8:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-26 13:29 Justin Piszcz
2011-03-27 23:25 ` Dave Chinner
2011-03-28  8:10   ` Justin Piszcz [this message]
2011-03-28 20:50     ` Dave Chinner
2011-03-28 20:54       ` Justin Piszcz

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=alpine.DEB.2.02.1103280406300.25113@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=david@fromorbit.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®