From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Christophe Saout <christophe@saout.de>
Cc: Andy Pfiffer <andyp@osdl.org>, <linux-kernel@vger.kernel.org>
Subject: Re: ext[23]/lilo/2.5.{68,69,70} -- IDE Problem?
Date: Thu, 12 Jun 2003 01:40:11 +0200 (MET DST) [thread overview]
Message-ID: <Pine.SOL.4.30.0306120136580.22297-100000@mion.elka.pw.edu.pl> (raw)
In-Reply-To: <1055373692.16483.8.camel@chtephan.cs.pocnet.net>
mm/msync.c:
<...>
* MS_ASYNC does not start I/O (it used to, up to 2.5.67).
<...>
You can revert changes to mm/msync.c from 2.5.68 patch
and see whether it helps.
Regards,
--
Bartlomiej
On 12 Jun 2003, Christophe Saout wrote:
> Am Don, 2003-06-12 um 00.08 schrieb Andy Pfiffer:
> > On Fri, 2003-05-09 at 13:55, Andy Pfiffer wrote:
> > > On Fri, 2003-05-09 at 13:04, Christophe Saout wrote:
> > > > Am Fre, 2003-05-09 um 21.04 schrieb Andy Pfiffer:
> > > >
> > > > > [...]
> > > > > I had an unrelated
> > > > > delay in posting this due to some strange behavior of late with LILO and
> > > > > my ext3-mounted /boot partition (/sbin/lilo would say that it updated,
> > > > > but a subsequent reboot would not include my new kernel)
> > > >
> > > > So I'm not the only one having this problem... I think I first saw this
> > > > with 2.5.68 but I'm not sure.
> > >
> > > Well, that makes two of us for sure.
> > >
> > > >
> > > > My boot partition is a small ext3 partition on a lvm2 volume accessed
> > > > over device-mapper (I've written a lilo patch for that, but the patch is
> > > > working and) but I don't think that has something to do with the
> > > > problem.
> > > >
> > > > When syncing, unmounting and waiting some time after running lilo, the
> > > > changes sometimes seem correctly written to disk, I don't know when
> > > > exactly.
> > >
> > > My /boot is an ext3 partition on an IDE disk. My symptoms and your
> > > symptoms match -- wait awhile, and it works okay. If you don't wait
> > > "long enough" the changes made in /etc/lilo.conf are not reflected in
> > > the after running /sbin/lilo and rebooting normally.
> > >
> > > I have been unable to reproduce this on a uniproc system with SCSI
> > > disks.
> > >
> > > 2.5.67 seems to work in this regard as expected.
> > >
> > > > Could it be that the location of /boot/map is not written to the
> > > > partition sector of /dev/hda? Or not flushed correctly or something?
> > > >
> > > > After reboot the old kernel came up again (though it was moved to
> > > > vmlinuz.old).
> > >
> > > I don't know -- I haven't isolated it yet.
> > >
> > > Anyone else?
> >
> > I have taken another look at this, and can confirm the following:
> >
> > 1. 2.5.67 works as expected.
> > 2. 2.5.68, 2.5.69, and 2.5.70 do not.
> > 3. ext2 vs. ext3 for /boot: no effect (ie, .68, .69, .70 demonstrate the
> > problem independent of the filesystem used for /boot).
>
> I found out that flushb /dev/<boot_device> helps, syncing doesn't. Not
> 100% sure if that's right, because right now I'm always doing both, but
> I remember having only synced before and that didn't help.
>
> > Relative to a 2.5.68 pure BK tree, the deltas from 2.5.67 to 2.5.68 are:
> > 1.971.76.10 /* 2.5.67 */
> > 1.1124 /* 2.5.68 */
> >
> > The patch exported by BK between these 2 revs is 297K lines ( a sizeable
> > haystack ). Any ideas about where I should dig for my needle first
> > would be welcomed...
>
> There don't seem to be too much changes in /drivers/block or /fs, mostly
> cleanups. I personally have no idea where to start, except trying out
> each -bk version inbetween. Hmmm. And I'm not going to do that now...
> :-/
>
> --
> Christophe Saout <christophe@saout.de>
next prev parent reply other threads:[~2003-06-11 23:27 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 [this message]
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
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=Pine.SOL.4.30.0306120136580.22297-100000@mion.elka.pw.edu.pl \
--to=b.zolnierkiewicz@elka.pw.edu.pl \
--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;
as well as URLs for NNTP newsgroup(s).