[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: problem using ext3 on root fs



On Mittwoch, 4. Dezember 2002 00:38, Theodore Ts'o wrote:
> OK, you're getting confused by a couple of things here.
>
> > During startup, my kernel emits the following lines:
> >
> > Kernel command line: auto BOOT_IMAGE=normal ro root=301 rootfstype=ext3 1
> > <lines deleted>
> > kjournald starting.  Commit interval 5 seconds
> > EXT3-fs: mounted filesystem with ordered data mode.
> > VFS: Mounted root (ext3 filesystem) readonly.
>
> The root filesystem is definitely getting mounted as ext3, with the
> root device as /dev/hda1 (major 3, minor 1).  This is a problem, you
> apparently have /dev/discs/dist0/part1 listed your /etc/fstab file.
> This is causing aliasing problems, but we'll talk about that in just a
> moment.

Yes, I noticed the aliasing, but I have no idea as to what it is caused
by. In lilo.conf I have:

root    = /dev/discs/disc0/part1

which is exactly what I have in /etc/fstab, however, it appears that
somehow this gets translated to 'root=301' before being passed to
the kernel. Could this be some kind of MS-style artificial intelligence
within lilo?

> Sorry, the maximum mount count checks still happen with
> journalling/ext3.  What ext3 protects you against needing to run fsck
> in case of an unclean shutdown.

Understood. This was a misconception about journaling on my side.

>
> The reason why the kernel is reporting the maximal mount count even
> after e2fsck is run because e2fsck is accessing the partition via the
> LVM device, because your /etc/fstab file specified
> /dev/discs/disc0/part1.  However, the kernel is accessing the
> filesystem via IDE device /dev/hda1.  This is a really bad thing,
> since it means that buffer cache can get out of sync.

The partition containing the root fs is not under LVM control. And, as
I am using devfs, there is nothing like '/dev/hda1' in my system.

tk
-- 
Thomas Koeller
thomas koeller dyndns org





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]