Bug 242985
| Summary: | kernel dm-crypt: OOM and lockup when using PAE kernel | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Daphne Shaw <dshaw> | ||||
| Component: | kernel | Assignee: | Milan Broz <mbroz> | ||||
| Status: | CLOSED RAWHIDE | QA Contact: | Corey Marthaler <cmarthal> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | rawhide | CC: | agk, ccb, cebbert, christophe.varoqui, davej, dwysocha, egoggin, jbrassow, junichi.nomura, kueda, lmb, mbroz, prockai, pvrabec, tranlan | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i386 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2008-03-30 02:50:35 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Daphne Shaw
2007-06-06 20:01:05 UTC
Also note that creating a dm-crypt device using a whole unpartitioned disk on the same machine (e.g. "/dev/sdb" instead of "/dev/sda9") works just fine. Please attach system info - memory size, syslog messages. Is it reproducible using standard (no PAE) kernel ? You can try to use lvmdump (from lvm2 package) to collect some info about system and attach it to this bz. Will help if you use sync between repeated mke2fs ? There were no lines at all logged in syslog (once the OOMing starts, things go
bad very quickly). There were some OOM reports on the console speeding by, but
none in syslog.
Here's memory info:
total used free shared buffers cached
Mem: 4142464 192156 3950308 0 76096 56992
-/+ buffers/cache: 59068 4083396
Swap: 3004144 0 3004144
Note that no swap is used, and the machine has plenty of free RAM as well when
it starts to OOM.
I will test your other questions shortly.
I just tested kernel-PAE-2.6.20-1.2952.fc6 against kernel-2.6.20-1.2952.fc6. I was able to repeat the failure using kernel-PAE-2.6.20-1.2952.fc6 I was NOT able to repeat the failure using kernel-2.6.20-1.2952.fc6 That is, it only fails with the PAE kernel. Sync-ing after each run did not make a difference on either PAE or non-PAE: PAE always failed, and non-PAE always succeeded. Can you get the contents of /proc/vmstat: (1) before running mke2fs (or is that what's above) (2) after each run of mke2fs that succeeeds Created attachment 157581 [details] Output of the crasher script Using this script, I can get the failure to happen within 3-4 runs. The attachment is the output. Note that run #3 didn't complete. # for i in `seq 1 10` > do > echo "Pass $i" >> output > echo BEFORE >> output > cat /proc/vmstat >> output > sync > mke2fs /dev/mapper/crypt-device > echo AFTER >> output > cat /proc/vmstat >> output > sync > done Kernel 2962 has dm-crypt bugfixes from 2.6.22 applied. Can you test that? It's in the updates-testing repo. I tested kernel 2962, and there is still a problem. It shows up in a slightly different fashion in that the machine freezes without first showing the OOMs on the console, but the end result is the same. I cannot reproduce this on 2.6.24-rc rawhide kernel (kernel-PAE-2.6.24-0.42.rc3.git1.fc9, using 6GB RAM) There were some changes (per BDI limits, dm-crypt bugfixes) in 2.6.24-rc kernel which, I think, should prevent that. (I expect that problem was related to committing too much work for internal crypt threads.) Please could you verify that it works with some 2.6.24 test kernel ? [changed fc6 -> fc-devel] |