From: Andrew Morton <akpm@zip.com.au>
To: Tom Rini <trini@kernel.crashing.org>
Cc: ext3-users@redhat.com, lkml <linux-kernel@vger.kernel.org>
Subject: Re: ext3-2.4-0.9.6
Date: Sat, 11 Aug 2001 18:55:05 -0700 [thread overview]
Message-ID: <3B75E1F9.2BF5D4B6@zip.com.au> (raw)
In-Reply-To: <3B75DE86.EEDFAFFB@zip.com.au>, <3B75DE86.EEDFAFFB@zip.com.au> <20010811184640.B17435@cpe-24-221-152-185.az.sprintbbd.net>
Tom Rini wrote:
>
> On Sat, Aug 11, 2001 at 06:40:22PM -0700, Andrew Morton wrote:
>
> > Patch against linux-2.4.8 is at
> >
> > http://www.uow.edu.au/~andrewm/linux/ext3/
> >
> > The only changes here are merging up to 2.4.8 and the bigendian
> > fix.
>
> Gack. I think about when you wrote this, I managed to crash again. I
> was running 2.4.8-pre8 + fsync_dev -> fsync_no_super + first fix. It
> was at transaction.c:1184, but the logs didn't make it to disk.
I'd assumed that this was related to the endianness fix. You're
sure you were running with that in place? If you can capture
a buffer trace that'd be great.
> 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.
Probably the simplest way to avoid this is to make the boot partition
ext2.
-
next prev parent reply other threads:[~2001-08-12 1:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-12 1:40 ext3-2.4-0.9.6 Andrew Morton
2001-08-12 1:46 ` ext3-2.4-0.9.6 Tom Rini
2001-08-12 1:55 ` Andrew Morton [this message]
2001-08-12 2:15 ` ext3-2.4-0.9.6 Tom Rini
2001-08-12 2:28 ` ext3-2.4-0.9.6 Andrew Morton
2001-08-12 2:47 ` ext3-2.4-0.9.6 Tom Rini
2001-08-12 4:58 ` ext3-2.4-0.9.6 Ben Collins
2001-08-13 18:15 ` ext3-2.4-0.9.6 Andreas Dilger
2001-08-12 2:38 ` ext3-2.4-0.9.6 Ralf Baechle
2001-08-12 3:10 ` ext3-2.4-0.9.6 Andrew Morton
2001-08-13 17:56 ` ext3-2.4-0.9.6 Stephen C. Tweedie
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=3B75E1F9.2BF5D4B6@zip.com.au \
--to=akpm@zip.com.au \
--cc=ext3-users@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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