Re: ext[23]/lilo/2.5.{68,69,70} -- blkdev_put() problem?

[Andrew Morton]

Christophe Saout <[e-mail]> 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' ;)