On Sat, Aug 11, 2001 at 07:28:51PM -0700, Andrew Morton wrote:
> Tom Rini wrote:
> > > > On a
> > > > related note, what does ext3 do to the disk when this happens, I
> > > > think I need to point the yaboot author at it since it couldn't
> > > > load a kernel (which was fun, let me tell you.. :))
> > >
> > > ext3 is designed to nicely crash the machine if it thinks something
> > > may be wrong with the fs - it's very defensive of your data.
> > >
> > > If yaboot is open firmware's native ext2 capability then presumably
> > > it refuses to read an ext3 partition which needs recovery. ext3
> > > is designed to not be compatible with ext2 when it's in the
> > > needs-recovery state.
> >
> > It's the linux bootloader that OF runs. Is there any 'safe' way to read
> > data off of an unclean ext3 partition? I'm thinking grub might run into
> > this problem too..
>
> Well, LILO works OK with an unclean ext3 FS because it goes straight to
> the underlying blocks. If both grub and OF parse the superblock compatibility
> bits then they could fail in this manner.
Both GRUB and yaboot can read directly from the fs. It's possible to boot
a kernel right out of OF from an HFS partition (which I had to do to get
the box up again). It might be worth documenting this someplace.
> I *think* that at present an unrecovered ext3 filesystem is "incomaptible"
> with ext2. If, however we were to make it "read-only compatible" then
> ext2-aware loaders would still be able to read the fs and boot from it.
That'd be nice. There's lots of PPC boxes which don't have a seperate
/boot. But ext2 should be able to read a clean ext3, yes? I never get
a chance to check thing... :)
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/