From: Andrew Morton <akpm@digeo.com>
To: Christophe Saout <christophe@saout.de>
Cc: andyp@osdl.org, adam@yggdrasil.com, linux-kernel@vger.kernel.org
Subject: Re: ext[23]/lilo/2.5.{68,69,70} -- blkdev_put() problem?
Date: Thu, 12 Jun 2003 03:54:42 -0700 [thread overview]
Message-ID: <20030612035442.29345778.akpm@digeo.com> (raw)
In-Reply-To: <1055414558.565.4.camel@chtephan.cs.pocnet.net>
Christophe Saout <christophe@saout.de> wrote:
>
> 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.
That would tend to imply that a page got onto the wrong list. But if that
were so, nothing would be able to write it.
> Only flushb /dev/hda does (or waiting several minutes).
What is flushb?
I use `lilo ; reboot -f' about 1000 times a day, no probs. There's
something different.
Adam was doing strange things with an initrd and pivot_root. Are you doing
anything unconventional?
>
> BTW: I found out that now strace lilo freezes the machine...
Works OK here. Try `strace strace lilo' ;)
next prev parent reply other threads:[~2003-06-12 10:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 19:04 [KEXEC][2.5.69] kexec for 2.5.69 available Andy Pfiffer
2003-05-09 20:04 ` ext3/lilo/2.5.6[89] (was: [KEXEC][2.5.69] kexec for 2.5.69 available) Christophe Saout
2003-05-09 20:55 ` Andy Pfiffer
2003-05-09 20:46 ` ext3/lilo/2.5.6[89] (was: [KEXEC][2.5.69] kexec for 2.5.69available) Riley Williams
2003-05-09 22:39 ` Joe Korty
2003-05-09 23:39 ` Andy Pfiffer
2003-06-11 22:08 ` ext[23]/lilo/2.5.{68,69,70} -- IDE Problem? Andy Pfiffer
2003-06-11 23:21 ` Christophe Saout
2003-06-11 23:40 ` Bartlomiej Zolnierkiewicz
2003-06-12 0:20 ` ext[23]/lilo/2.5.{68,69,70} -- blkdev_put() problem? Andy Pfiffer
2003-06-12 0:29 ` Andrew Morton
2003-06-12 10:42 ` Christophe Saout
2003-06-12 10:54 ` Andrew Morton [this message]
2003-06-12 11:12 ` Christophe Saout
2003-06-12 11:24 ` ext[23]/lilo/2.5.{68,69,70} -- strace lilo - freeze Christophe Saout
2003-06-12 12:44 ` ext[23]/lilo/2.5.{68,69,70} -- blkdev_put() problem? Herbert Xu
2003-06-12 17:27 ` Andy Pfiffer
2003-06-12 17:53 ` Andrew Morton
2003-06-12 18:03 ` Andy Pfiffer
2003-06-12 18:10 ` Andrew Morton
2003-06-12 18:53 ` Christophe Saout
2003-06-12 18:25 ` Andy Pfiffer
2003-06-13 8:01 ` Andrew Morton
2003-06-13 9:57 ` Herbert Xu
2003-06-13 14:42 ` Eduardo Pereira Habkost
2003-06-13 17:17 ` Andy Pfiffer
2003-06-13 22:12 ` Unai Garro Arrazola
2003-06-13 22:28 ` Andrew Morton
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=20030612035442.29345778.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=adam@yggdrasil.com \
--cc=andyp@osdl.org \
--cc=christophe@saout.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®