Bug 128488 - can't update nfract_stop_bdflush
can't update nfract_stop_bdflush
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: kernel (Show other bugs)
2.1
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Jason Baron
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-07-23 11:44 EDT by David Muller
Modified: 2013-03-06 00:57 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-11-04 15:32:21 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description David Muller 2004-07-23 11:44:51 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
cannot change nfract_stop_bdflush parameter in /proc/sys/vm/bdflush

We've tried both echoing value in and setting in rc.local and 
rebooting - neither works.  We are trying to tune vm settings in 
short term while we work on upgrade to AS 3.0.

Version-Release number of selected component (if applicable):
2.4.9-e.27enterprise #1 SMP Tue Aug 5 15:39:21

How reproducible:
Always

Steps to Reproduce:
1.echo "40      128     512     2048    500     3000    80      
40       0" > /proc/sys/vm/bdflush
2. more /proc/sys/vm/bdflush
3.
    

Actual Results:  more /proc/sys/vm/bdflush
40      128     512     2048    500     3000    80      0       0


Expected Results:  change to 40

Additional info:
Comment 1 Suzanne Hillman 2004-07-27 16:51:10 EDT
This looks like something for which you would be best off contacting
support:

https://www.redhat.com/apps/support/
Comment 2 Jason Baron 2004-08-17 16:10:10 EDT
the nfract_stop_bdflush parameter is not implemented for rhel2.1...is
there a good reason that we should add it?
Comment 3 Jason Baron 2004-11-04 15:32:21 EST
No updates...closing.

Note You need to log in before you can comment on or make changes to this bug.