Bug 232276 - Kernel hangs working with crypted loop device
Kernel hangs working with crypted loop device
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
4.4
i386 Linux
medium Severity urgent
: ---
: ---
Assigned To: Red Hat Kernel Manager
Martin Jenner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-14 13:27 EDT by Artem S. Tashkinov
Modified: 2007-11-16 20:14 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-11-15 17:49:06 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
A script in use (5.41 KB, text/plain)
2007-03-14 13:27 EDT, Artem S. Tashkinov
no flags Details

  None (edit)
Description Artem S. Tashkinov 2007-03-14 13:27:59 EDT
Description of problem: kernel hangs when writing multiple files simultaneously
on a filesystem which remains on a encrypted loop device (represented by a file
which remains a on a NFS share).

Version-Release number of selected component (if applicable): 2.6.9-42.0.3.ELsmp

How reproducible: always, the bug doesn't trigger if you just read files

Steps to Reproduce:
1. Use the attached script to create a large enough FS image (on our production
server it's a 200GB file)
2. Use any other script or application which is able to create and write at
least ten files _concurrently_ in different directories (we have four level nesting)
3. Under such circumstances our server becomes entirely unresponsive, it either
hangs instantly, or it runs for around hour or two without allowing writing any
files to any  HDDs - so no SSH logins, crond tasks cannot start ... then it
hangs. If you are logged on at this time - you cannot even run top or ps - they
both hang at startup.
  
Actual results: hang


Expected results: work


Additional info:

1) I suppose this bug is not hardware related. This server (two Prescott based
Xeon CPUs) is located in a server room where temperature doesn't ever exceeds 20
degrees Celsius.

2) Usually when this server hangs a load average value is around 70-200.
Comment 1 Artem S. Tashkinov 2007-03-14 13:27:59 EDT
Created attachment 150068 [details]
A script in use
Comment 2 Artem S. Tashkinov 2007-10-20 09:45:41 EDT
You tried to change the Status field from NEW to CLOSED, but only the owner or
submitter of the bug, or a autorized user, may change that field. 
Comment 3 Chuck Ebbert 2007-10-21 11:45:20 EDT
(In reply to comment #2)
> You tried to change the Status field from NEW to CLOSED, but only the owner or
> submitter of the bug, or a autorized user, may change that field. 

Why do you want to close the bug?
Comment 4 Artem S. Tashkinov 2007-10-21 14:21:07 EDT
Due to frequent kernel crashes, we retracted from using this solution. Besides
in seven (!) months you are the first person to notice this bug. My employer
couldn't wait for seven months - since that we implemented a different solution.
Comment 5 Chuck Ebbert 2007-10-22 12:14:56 EDT
Bug was not assigned properly. kernel-maint is for the Fedora kernel.

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