Bug 1458916
| Summary: | SHM* Sysctls were not increased for s390 systems | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Charles Haithcock <chaithco> |
| Component: | initscripts | Assignee: | David Kaferad // Dee'Kej <deekej> |
| Status: | CLOSED DUPLICATE | QA Contact: | qe-baseos-daemons |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.4 | CC: | deekej, hannsj_uhl, initscripts-maint-list |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | s390 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-04-27 13:27:40 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1420851, 1465901, 1466365, 1549689 | ||
I am not sure it would be wise to change the defaults. And you can easily override this through another sysctl.d drop-in. Anyway let's move this decision to 7.5 since we already passed beta. (In reply to Lukáš Nykrýn from comment #3) > I am not sure it would be wise to change the defaults. And you can easily > override this through another sysctl.d drop-in. > > Anyway let's move this decision to 7.5 since we already passed beta. Thanks for that correction, I seemed to have missed that. For the defaults, I (potentially incorrectly) assumed the same should be done for s390 systems since we rolled back the sysctls for other arches. If we need to keep the sysctls where they are for s390 systems, then we of course can, but we will need the reasoning mentioned somewhere. From there, I can open a BZ with the docs team as our docs currently make no indication or warning about the difference between s390 systems and otherwise. (In reply to Charles Haithcock from comment #4) > For the defaults, I (potentially incorrectly) assumed the same should be > done for s390 systems since we rolled back the sysctls for other arches. If > we need to keep the sysctls where they are for s390 systems, then we of > course can, but we will need the reasoning mentioned somewhere. From there, > I can open a BZ with the docs team as our docs currently make no indication > or warning about the difference between s390 systems and otherwise. Hello Charles, we were discussing this today, and none of us remember why that configuration wasn't also removed for s390x. We have come to 2 conclusions: 1) Either this is a mistake on our side that we forgot to remove that configuration, or 2) it was left there intentionally for some reasons we are not aware ATM (we are no experts on s390x). As a result, we have decided to postpone the final decision what to do about this, and during that time we will try to reach out to IBM people to consult this with them. Anyway, in the meantime, you can use workaround as suggested by Lukas... ;) Best regards, David > 1) Either this is a mistake on our side that we forgot to remove that > configuration, or > 2) it was left there intentionally for some reasons we are not aware ATM (we > are no experts on s390x). Understood; I had the same thoughts as well. > As a result, we have decided to postpone the final decision what to do about > this, and during that time we will try to reach out to IBM people to consult > this with them. Sounds good! > Anyway, in the meantime, you can use workaround as suggested by Lukas... ;) Absolutely; my customer is fine with simply putting in a custom sysctl.conf file. Fortunately this is not a huge deal for them (as it shouldn't be). The pull-request to resolve this has been submitted: https://github.com/fedora-sysv/initscripts/pull/182 We have other BZ for tracking this issue, so I'm closing this one as a duplicate. If you need to follow up with more information, please do so in BZ #1493069... -- David -- *** This bug has been marked as a duplicate of bug 1493069 *** |
Description of problem: shm* sysctls were introduced to lower the shm* sysctls for the system to lower values but were removed in later releases except for s390 systems. Version-Release number of selected component (if applicable): RHEL 7.2-3 How reproducible: 100% Steps to Reproduce: 1. Install RHEL 7 onto an s390 system 2. run `sysctl -q kernel.{shmmax,shmall}` and check `grep shm /usr/lib/sysctl.d/00-system.conf` Actual results: [root@gss3 ~]# sysctl -q kernel.{shmmax,shmall} kernel.shmmax = 4294967295 kernel.shmall = 268435456 [root@gss3 ~]# grep shm /usr/lib/sysctl.d/00-system.conf kernel.shmmax = 4294967295 kernel.shmall = 268435456 Expected results: [root@gss3 ~]# sysctl -q kernel.{shmmax,shmall} kernel.shmmax = 18446744073692774399 kernel.shmall = 18446744073692774399 [root@gss3 ~]# grep shm /usr/lib/sysctl.d/00-system.conf -c 0 Additional Info: Relevant BZs introducing the shm increases and rollbacks to shm* sysctls: - BZ1056547: also contains motivation for rollback in comment 15 - BZ1150130: introduction of shm* being set to ULONG_MAX - 2^24 - BZ1222403: backport sysctl rollback to 7.1 - BZ1101821: 7.1