Bug 2037392
| Summary: | zram generaor with writeback device - permission denied | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Igor Bukanov <igor> |
| Component: | rust-zram-generator | Assignee: | Rust SIG <rust-sig> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 35 | CC: | rust-sig, zbyszek |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | rust-zram-generator-1.1.2-1.fc35 rust-zram-generator-1.1.2-1.fc36 rust-zram-generator-1.1.2-1.fc34 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-03-31 01:15:01 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: | |||
|
Description
Igor Bukanov
2022-01-05 14:41:13 UTC
It turned out Fedora kernel is not compiled with the CONFIG_ZRAM_WRITEBACK option. Thus, when zram-generator tries to write to /sys/block/zram0/backing_dev, it got the permission denied error. Still it will be nice if zram-generator can detect the absence of /sys/block/zramN/backing_dev and report that zram backing is not supported. Currently the error does not even include the name of the file zram-generator ties to write. FEDORA-2022-5e0fef8466 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5e0fef8466 FEDORA-2022-c7f28019a2 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-c7f28019a2 FEDORA-2022-95003a8fd5 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-95003a8fd5 FEDORA-2022-5e0fef8466 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-5e0fef8466` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-5e0fef8466 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-95003a8fd5 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-95003a8fd5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-95003a8fd5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-c7f28019a2 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-c7f28019a2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-c7f28019a2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-95003a8fd5 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-5e0fef8466 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-c7f28019a2 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. |