All of lore.kernel.org
 help / color / mirror / Atom feed
From: Floydsmith@aol.com
To: linux-kernel@vger.kernel.org
Cc: Floydsmith@aol.com
Subject: can't get buffer cache to flush with /dev/ram with 2.2.4 using "update"/"sync"
Date: Sat, 4 Aug 2001 12:52:36 EDT	[thread overview]
Message-ID: <c0.181ed0fb.289d8254@aol.com> (raw)

Hello all,

I boot linux using "loadlin" with an "initrd" ram disk image ("minix" type 
fs) of size 32 Meg with kernel 2.2.4. The /linuxrc (a C executable) runs and 
it shows that the mounted file sysem is of proper type and size. Then my 
"linuxrc" extracts a "tar" achrive (to populate the mounted /dev/ram [on 
"/"]) with a small subset of  "linux" about (18 Meg) (as a "rescue" floppy 
boot). Before the "extract", debug code shows that the "cached" entry in 
"/proc/meminfo" to be practically zero (and thus plenty of "freemem"). 
However, after the "extract", the "cached" line shows about "18Meg"  and I 
can find nothing that works to "flush" it. I have tried "spawing" 
"/sbin/update" and waiting several min. and running "/bin/sync" and also 
waiting - no change in the "cahed" entry (or and increase in the "freemem").  
(ps -ef shows a process "bdflush" running [spawned] on its own.) Thus, trying 
to bring up a "logon" shell (and its "init" scripts) results in that process 
being killed do to lack of "freemem". I have only 64M and less than 4 Meg 
free after the "extract". Any suggestions greatly appreciated in advance. If 
there any "syscall" I can make in "linuxrc" that will flush "all" buffers 
without knowing anything like "file descriptors"? Is this "syscall" 
"synchronus" - or do do I have wait several seconds for it to work?

Floyd,

                 reply	other threads:[~2001-08-04 16:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c0.181ed0fb.289d8254@aol.com \
    --to=floydsmith@aol.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.