Anton Altaparmakov wrote:
>
> At 19:12 07/11/2001, Alan Cox wrote:
> > > when coming back up it fscked (I didn't touch anything - didn't even
> > notice
> > > any 5 second thing but I wasn't looking at this screen) and it found two
> > > lost inodes (I got two entries in lost and found). So it still needs to
> > > fsck by the looks of it?
> >
> >That sounds like you used your own kernel with it and had ext2 mounting
> >the root fs (remember its back compatible)
>
> Yes, that makes a lot of sense. After the reset I went into my own kernel
> with both ext2 and ext3 compiled into it. However, before the reboot, I was
> still in the RH kernel (99% sure it was so, but my memory might be
> deceiving me).
>
> Is there any Right Way(TM) to fix this situation considering I want to have
> both ext2 and ext3 in my kernels (apart from the obvious of changing the
> order fs are called during root mount in the kernel)?
>
There's a fair bit of material on this at
http://www.uow.edu.au/~andrewm/linux/ext3/ext3-usage.html
executive summary:
- use latest util-linux and e2fsprogs
- Make the root fs have fstype `ext3' in /etc/fstab
- Make the others `auto'
- Alternatively, use "ext3,ext2" in fstab.
The problem is that various tools (mount, fsck, df, others?)
make various assumptions about what to do when certain
filesystem types are encountered in fstab. It's been a bit
painful.
-
-
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/
This archive was generated by hypermail 2b29 : Wed Nov 07 2001 - 21:00:36 EST