Bug 450014 - Processes stuck in D state
Processes stuck in D state
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
i386 Linux
low Severity high
: rc
: ---
Assigned To: Red Hat Kernel Manager
Martin Jenner
Depends On:
  Show dependency treegraph
Reported: 2008-06-04 15:09 EDT by R.H.
Modified: 2012-06-20 12:19 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 12:19:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description R.H. 2008-06-04 15:09:22 EDT
Description of problem:
We are seeing poor performance and note processes spending too much time in
uninterruptible sleep.

It seems to be coupled to having a large number of files/dirs as we have an
apache cache with 2,000,000 entries and the problem is apparent.  Before the
cache has any entries things are more responsive.

Version-Release number of selected component (if applicable):
2.6.9-67.0.15.ELhugemem #1 SMP Tue Apr 22 14:01:33 EDT 2008 i686 i686 i386 GNU/Linux

How reproducible:
1. create an ext3 filesystem, create 64 directories each with 64 directories and
each again with 64 directories, total 64^3 directories 

2. create some files in all those

3. then run find . -type f

4. then run ps -eo pid,stat,wchan:40,comm |grep D

Actual results:

 PID STAT WCHAN                                    COMMAND
21878 D+   wait_on_buffer                           find

Expected results:

Not that above.
Comment 1 Jiri Pallich 2012-06-20 12:19:29 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

Note You need to log in before you can comment on or make changes to this bug.