Bug 912848
| Summary: | RFE: dmsquash-live: Support variable temporary overlay size | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | fedora.dm0 | ||||
| Component: | dracut | Assignee: | dracut-maint | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rawhide | CC: | dracut-maint, fgrose, jonathan | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-10-02 19:30:12 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
This was implemented in commit, http://git.kernel.org/cgit/boot/dracut/dracut.git/commit/?id=18423f7951de7b9cb4007438b58b6067aa6f2e93 It seems to work since that commit. Thanks, I'll close the bug. |
Created attachment 699618 [details] Add an option to adjust the RAM-based overlay size This is a request to allow users to adjust the size of the temporary (RAM-based) overlay for live CDs. It is currently hard-coded to provide 512MB of writable space. Use case: I will often simply boot a stock live CD of various Fedora releases to quickly test software builds for compatibility. (It gives a consistent environment each time with a typical package set, and the ISOs are easy to locate.) However, a while after each release, package updates start to accumulate. Retrieving a devel RPM can easily cause an avalanche of updates/dependencies to fill the available 512MB, between the yum cache and installed files. The rest of my workstation's 16GB of RAM can only sit and watch as I/O errors fill the screen. So the attached patch is an example of something I had in mind: a boot argument for specifying the overlay size in MB (which defaults to the existing behavior). I would be happy to accept other recommended solutions as well, like maybe an option to copy the ext4 filesystem into RAM (instead of squashfs) and then drop the overlay all together.