linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Riley Williams" <Riley@Williams.Name>
To: "Andy Pfiffer" <andyp@osdl.org>,
	"Christophe Saout" <christophe@saout.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: ext3/lilo/2.5.6[89] (was: [KEXEC][2.5.69] kexec for 2.5.69available)
Date: Fri, 9 May 2003 21:46:50 +0100	[thread overview]
Message-ID: <BKEGKPICNAKILKJKMHCACEJHCLAA.Riley@Williams.Name> (raw)
In-Reply-To: <1052513725.15923.45.camel@andyp.pdx.osdl.net>

Hi Andy, Christophe.

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

One suggestion: ext3 is a journalled version of ext2, so if you can
boot with whatever is needed to specify that the boot partition is
to be mounted as ext2 rather than ext3, you can isolate the journal
system: If the problem's still there in ext2 then the journal is
not involved, but if the problem vanishes there, it's something to
do with the journal.

I have to admit that the above sounds very much like the details
are being recorded in the journal, but the journal isn't being
played back to update the actual files.

Best wishes from Riley.
---
 * Nothing as pretty as a smile, nothing as ugly as a frown.

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.478 / Virus Database: 275 - Release Date: 6-May-2003


  reply	other threads:[~2003-05-09 21:34 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     ` Riley Williams [this message]
2003-05-09 22:39       ` ext3/lilo/2.5.6[89] (was: [KEXEC][2.5.69] kexec for 2.5.69available) 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
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=BKEGKPICNAKILKJKMHCACEJHCLAA.Riley@Williams.Name \
    --to=riley@williams.name \
    --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).