lkml.org 
[lkml]   [2003]   [Jun]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: ext[23]/lilo/2.5.{68,69,70} -- blkdev_put() problem?
From
Date
Am Don, 2003-06-12 um 02.29 schrieb Andrew Morton:

> But sync() should certainly write everything out, and lilo does perform a
> sync.

Yep.

> I'd be interested in seeing the contents of /proc/meminfo immediately after
> the lilo run, see if there's any dirty memory left around.

Yes, one page. After running lilo, there are 4k diry, running sync
doesn't get it below 4k. Only flushb /dev/hda does (or waiting several
minutes).

If you're interested, I've put an annotated version of

( cat /proc/meminfo; lilo; cat /proc/meminfo; sync; cat /proc/meminfo;
flushb /dev/hda; cat /proc/meminfo ) | buffer > meminfo.out.txt

on my web space: http://www.saout.de/files/meminfo.out.txt

(the kernel used was 2.5.70-mm7 with some unrelated patches backed out)

BTW: I found out that now strace lilo freezes the machine...

--
Christophe Saout <christophe@saout.de>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:36    [W:0.068 / U:12.492 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site