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

[Christophe Saout <christophe@saout.de>]

Am Don, 2003-06-12 um 12.54 schrieb Andrew Morton:

> Christophe Saout <christophe@saout.de> wrote:
> >
> > Am Don, 2003-06-12 um 02.29 schrieb Andrew Morton:
> >
> > > 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?

A program that does a flush ioctl on a block device:

open("/dev/hda", O_RDONLY)              = 3
ioctl(3, BLKFLSBUF, 0)                  = 0

> 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?

I'm using an initrd (but no pivot_root) that initializes my LVM2 volumes
(using device-mapper).

/boot and / are on device-mapper devices.

> > BTW: I found out that now strace lilo freezes the machine...
> 
> Works OK here.  Try `strace strace lilo' ;)

I'll try to find out what happens. Not interested in crashing my system
while answering emails now. ;)

-- 
Christophe Saout <christophe@saout.de>