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

Re: root fs type in fstab



On Thu, Jan 18, 2001 at 05:03:46PM -0700, Andreas Dilger wrote:
> 
> However, if there is a possibility of segfaulting in e2fsck, it should
> also be tracked down, because it will happen again sooner or later with
> some other corrupt journal, so it still needs to be fixed.  Having a
> 100% reproducable problem makes it easier to find.
 
OK.  Here's the stack trace:

#0 0x80c13a8 in main_arena ()
#1 0x8055f17 in fatal_error (ctx=0x80c4150, msg=0x0) at util.c:43
#2 0x8055555 in e2fsck_run_ext3_journal (ctx=0x80c4150) at journal.c:713
#3 0x8049a43 in main (argc=4, argv=0xbffffde4) at unix.c:807
#4 0x8064741 in __libc_start_main (main=0x8049414 <main>, argc=4,
   ubp_av=0xbffffde4, init=0x80480b4 <_init>, fini=0x80ab5ao <_fini>,
   rtld_fini=0, stack_end=0xbffffddc) at ../sysdeps/generic/libc-start.c:111

It looks like ctx->fs->io was smashed.  It has garbage values in it.  The
"flush" method in *ctx->fs->io->manager has been smashed too:

(gdb) print *ctx->fs->io->manager->flush
$7 = {errcode_t ()} 0x80c13a0 <main_arena+320>

which is of course, why the SIGSEGV.

I have the gdb session running still if you want more data.  Please just
keep in mind that it is on the VGA console of a machine that was stopped
in rc.sysinit so no access other than keyboard and eyes.  Anything you
want I will have to copy by hand from the screen so please be merciful.
:-)

b.





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