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

Re: root fs type in fstab



Brian, you write:
> 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

At least knowing where to start looking is a help.  I don't know that I
can get to this in a reasonable time, unless you are OK with leaving the
machine idle for up to a week or so.

> 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:

This is exactly what my SEGV was, and I fixed it by verifying the I/O
manager magic before calling the "flush" method.


-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert





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