high load and xfsaild in d

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello all,

I recently deployed a new CentOS 6.3 file server, and soon after I
noticed that the load was consistenly at around 4, even with no obvious
activity.  After checking around a bit, the only unusual thing I could
find is that the xfsaild threads are all consistently in D state:

root      1744  0.0  0.0      0     0 ?        D    Nov16   7:46 [xfsaild/dm-2]
root      1756  0.0  0.0      0     0 ?        D    Nov16   7:44 [xfsaild/dm-1]
root      1759  0.0  0.0      0     0 ?        D    Nov16   7:57 [xfsaild/dm-3]
root      1762  0.0  0.0      0     0 ?        D    Nov16   5:59 [xfsaild/dm-0]

On another CentOS 6.2 box, I don't see this symptom; the xfsaild threads
are all in S state.  I checked around for many other things that I'd
normally expect to be pegging the load, but didn't find anything out of
the ordinary.  (See
https://groups.google.com/group/comp.os.linux.misc/browse_thread/thread/c9b2a1d60eb25fac
for more details.)

The new box is an up to date CentOS 6.3 box with the stock kernel:

Linux xxxxxxxx 2.6.32-279.14.1.el6.x86_64 #1 SMP Tue Nov 6 23:43:09 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

The storage backends are a software RAID1 (three of the filesystems) and
a 3ware 9750-backed 11-disk RAID6.  I don't have any unusual mount
options, and the filesystems were created with mkfs.xfs with no options.

I searched the web and the list archives, and did find some issues with
xfsaild, but they all either seemed out of date (one thread mentioned
that an issue would be fixed in 2.6.30) or with more complicated
symptoms (other processes hanging in D state).  But this server seems
perfectly fine from what I can tell; I've noticed no performance issues
either in informal observations or with actual measured read/write
speeds, and the smbd and nfsd processes are all generally in S, so they
are not waiting on IO.

The big question is, is this actually a problem, or is it nothing to
worry about?  If it's a problem, is it in XFS, or if not, what other
steps can I take to try to determine the root cause?

Thanks,

--keith

-- 
kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx


_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs


[Index of Archives]     [Linux XFS Devel]     [Linux Filesystem Development]     [Filesystem Testing]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux