Bug 812351
Summary: | mke2fs on 15TB volume requires 728084kB mem, causing OOM | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Alexander Todorov <atodorov> | ||||
Component: | e2fsprogs | Assignee: | Eric Sandeen <esandeen> | ||||
Status: | CLOSED NOTABUG | QA Contact: | BaseOS QE - Apps <qe-baseos-apps> | ||||
Severity: | urgent | Docs Contact: | |||||
Priority: | urgent | ||||||
Version: | 6.3 | CC: | rwheeler, sct | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Unspecified | ||||||
Whiteboard: | abrt_hash:09c548cdca9f8301bb598222638fdaff9d307ae632e56f330a7d31e1e4072192 | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2012-07-28 12:23:24 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: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 760559, 767727, 840699 | ||||||
Attachments: |
|
Description
Alexander Todorov
2012-04-13 13:29:53 UTC
Created attachment 577338 [details]
File: anaconda-tb-3oFRBC
Reproduced during testing another bug. See steps to reproduce: https://bugzilla.redhat.com/show_bug.cgi?id=767727#c5 Quoting the other bug: Tested with ks.cfg configuration from comment #0 and two sparse disk images. Each sized 16492674416641 bytes. # dd if=/dev/zero of=large2.img seek=15T count=1 bs=1 I hit bug 812351. Is this still happening on the latest 6.3 nightly trees? (In reply to comment #4) > Is this still happening on the latest 6.3 nightly trees? Yes, I tested with snapshot #5 which is the most recent working tree I have ATM. 17:28:14,436 ERR kernel:Out of memory: Kill process 1409 (mke2fs) score 565 or sacrifice child 17:28:14,436 ERR kernel:Killed process 1409, UID 0, (mke2fs) total-vm:728084kB, anon-rss:606672kB, file-rss:8kB 13:27:34,596 INFO : Detected 1008M of memory 13:27:34,596 INFO : Swap attempt of 1008M to 1008M Isn't that not enough? I also have swap space available. David, is it expected that mke2fs consumes that much memory when creating a large filesystem ? iow is there a memory leak in mke2fs? OTOH shouldn't we make use of the available swap space? (In reply to comment #7) > 13:27:34,596 INFO : Detected 1008M of memory > 13:27:34,596 INFO : Swap attempt of 1008M to 1008M > > Isn't that not enough? I also have swap space available. > > David, > is it expected that mke2fs consumes that much memory when creating a large > filesystem ? iow is there a memory leak in mke2fs? That sure looks like a lot of memory to me. > OTOH shouldn't we make use of the available swap space? Activating swap early is non-trivial in many cases as it requires enforcing an artificial ordering constraint on the storage creation/activation operations. Reassigning to e2fsprogs as anaconda cannot do anything about how much memory the tools require to create huge filesystems. If there's no bug there, maybe a release note would be appropriate. You need to size your memory to the size of the file system you need to create, we don't have current plans to fix this so I will close out this BZ. Note that other file systems (XFS or btrfs) will do better here. |