sysctl -p doesn't work on vm.dirty_background_bytes = 0

Bug #821603 reported by Sworddragon on 2011-08-05
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
procps (Ubuntu)
Undecided
Unassigned

Bug Description

I'm using Ubuntu 11.10 dev. For example set vm.dirty_background_bytes to 1048676, execute "sysctl -p" and then check the value with "sysctl -a | grep 'vm\.'". vm.dirty_background_bytes is now set to 1048676 as expected. But if vm.dirty_background_bytes is now set to 0, "sysctl -p" is executed and the value is checked with "sysctl -a | grep 'vm\.'" it still shows 1048676 instead of 0.
---
Architecture: amd64
DistroRelease: Ubuntu 11.10
EcryptfsInUse: Yes
NonfreeKernelModules: nvidia
Package: procps 1:3.2.8-10ubuntu5
PackageArchitecture: amd64
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0
Tags: oneiric
Uname: Linux 3.0.0-7-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout lpadmin plugdev sambashare sudo

komputes (komputes) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 821603

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: ubuntu → procps (Ubuntu)
Changed in procps (Ubuntu):
status: New → Incomplete

apport information

tags: added: apport-collected oneiric
description: updated
Changed in procps (Ubuntu):
status: Incomplete → New
Peter Cordes (peter-cordes) wrote :

Did you try setting it to a non-zero value other than the default, if 1048676 was the default? Also, did you check that the value isn't getting overwritten by a later line in the same or a later config file in /etc/sysctl.d?

Sworddragon (sworddragon) wrote :

> Did you try setting it to a non-zero value other than the default, if 1048676 was the default?

I have tried this now and it behaves like 0.

> Also, did you check that the value isn't getting overwritten by a later line in the same or a later config file in /etc/sysctl.d?

Yes, sysctl is even telling me that it wanted to apply 0:

root@ubuntu:~# sysctl -p
vm.dirty_background_bytes = 0
root@ubuntu:~# sysctl -a | grep 'vm\.dirty_background_bytes'
vm.dirty_background_bytes = 1048576

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers