Messages in this thread | ![/](/images/icornerl.gif) | | Subject | RE: ext3/lilo/2.5.6[89] (was: [KEXEC][2.5.69] kexec for 2.5.69available) | From | Andy Pfiffer <> | Date | 09 May 2003 16:39:23 -0700 |
| |
On Fri, 2003-05-09 at 13:46, Riley Williams wrote: > 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.
Changing the "ext3" to "ext2" in /etc/fstab and rebooting did not change the behavior (ie, edit /etc/lilo.conf, run /sbin/lilo, reboot cleanly, changes not there). I did see the warning about mounting an ext3 filesystem as ext2, however.
Strange.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| ![\](/images/icornerr.gif) |