Re: 2.6.38.1: CPU#0 stuck for 67s! / xfs_ail_splice
From: Justin Piszcz
Date: Mon Mar 28 2011 - 04:10:27 EST
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/