All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Sarath Menon <sarathmenon@gmail.com>
Cc: reiserfs-list@namesys.com
Subject: Re: fsck.reiser4 segfaults
Date: Mon, 03 Apr 2006 14:21:42 +0400	[thread overview]
Message-ID: <1144059702.6316.62.camel@tribesman.namesys.com> (raw)
In-Reply-To: <932539950603311021x201d9e13mfdf9e95923e1f744@mail.gmail.com>

Hello

On Fri, 2006-03-31 at 20:21 +0200, Sarath Menon wrote:
> reiserfsprogs and libaal are both 1.0.5. I'll give you the dmesg
> output tommorow - I need to get a livecd with reiser4 patches - its
> more difficult than I initially thought ;)
> 
> Here's the gdb bt output - that's the max that I can provide today.
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x40052dd1 in repair_filter_update_traverse () from /tmp/reiser4/lib
> (gdb) bt
> #0  0x40052dd1 in repair_filter_update_traverse () from /tmp/reiser4
> #1  0x40015959 in reiser4_tree_trav_node () from /tmp/reiser4/lib/li
> #2  0x40015938 in reiser4_tree_trav_node () from /tmp/reiser4/lib/li
> #3  0x40052356 in repair_filter_traverse () from /tmp/reiser4/lib/li
> #4  0x40051c8c in repair_filter () from /tmp/reiser4/lib/librepair-1
> #5  0x400575ea in repair_check () from /tmp/reiser4/lib/librepair-1.
> #6  0x0804a1cb in main ()
> #7  0x4102eda6 in __libc_start_main () from /lib/libc.so.6
> 
> I'll post the dmesg output tommorow.
> 

I would like to debug this problem. Can you please do
debugfs.reiser4 /dev/thatdevice -P | bzip2 -c > reiser4-metadata.bz2
and put resulting file somewhere for downloading. That should make
debugging easier.

> Thanks,
> Sarath
> 
> On 3/31/06, Vladimir V. Saveliev <vs@namesys.com> wrote:
> > Hello
> >
> > On Fri, 2006-03-31 at 16:21 +0200, Sarath Menon wrote:
> > > Hello,
> > >
> > > I've been using reiser4 for more than a year without any problems. The
> > > filesystem performance has been commendable to say the least.
> > > Yesterday, I had to powercycle my pc (due to a dma hang with my cd
> > > drive - happens occasionaly) and after the reboot, grub would not
> > > load. I use a single root partition (/boot inclusive) and the patched
> > > grub sources.
> > >
> > > I've tried booting into knoppix and compiling reiser4progs and running an
> > fsck.
> > >
> > > This is what I get -:
> > > Master super block (16):
> > > magic:          ReIsEr4
> > > blksize:        4096
> > > format:         0x0 (format40)
> > > label:          <none>
> > >
> > > Format super block (17):
> > > plugin:         format40
> > > description:    Disk-format for reiser4.
> > > magic:          ReIsEr40FoRmAt
> > > flushes:        0
> > > mkfs id:        0x3a4f3c7b
> > > blocks:         2443880
> > > free blocks:    428490
> > > root block:     743745
> > > tail policy:    0x2 (smart)
> > > next oid:       0xf63a06
> > > file count:     469920
> > > tree height:    5
> > > key policy:     LARGE
> > >
> > >
> > > CHECKING STORAGE TREE
> > > FSCK: Node (743744), item (0), unit (0): Points to the block (743745)
> > > which is in the tree already.
> > > The whole subtree is skipped.
> > > Segmentation fault
> > >
> >
> > can you please run dmesg after that and send its output?
> >
> > > debugfs.reiser4 also segfaults, and a mount also fails, it complians
> > > of a duplicate key. (I can't post the exact message because the second
> > > livecd doesn't have X or any mail client :(
> > >
> > >
> > > Cheers,
> > > Sarath
> > >
> > > --
> > > I presume, when you pronounce iptables, you say that you are peeing tables
> > >
> >
> >
> 
> 
> --
> --------------------------
> I presume, when you pronounce iptables, you say that you are peeing tables
> 


  parent reply	other threads:[~2006-04-03 10:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-31 14:21 fsck.reiser4 segfaults Sarath Menon
2006-03-31 16:17 ` Vladimir V. Saveliev
2006-03-31 16:32 ` Vladimir V. Saveliev
2006-03-31 18:21   ` Sarath Menon
2006-03-31 20:21     ` Michael Weissenbacher
2006-04-01  6:02       ` Joachim Feise
2006-04-01  8:13         ` Sarath Menon
2006-04-01  9:02           ` Jake Maciejewski
2006-04-03 10:21     ` Vladimir V. Saveliev [this message]
     [not found]       ` <932539950604041657t42d33902s34dc8abcf056aa49@mail.gmail.com>
2006-04-05  0:00         ` Sarath Menon
2006-07-07  6:46       ` Sarath Menon
  -- strict thread matches above, loose matches on Subject: below --
2006-08-09 13:03 Jussi Suutari-Jaasko
2006-08-10  8:19 ` Jussi Suutari-Jääskö
2004-07-15 11:59 Konstantin Sobolev
2004-07-15 12:21 ` Vitaly Fertman
2004-07-15 18:45   ` Konstantin Sobolev
2004-07-15 19:09     ` Vitaly Fertman
2004-07-15 19:22       ` Konstantin Sobolev
2004-07-16  9:33         ` mjt
2004-07-15 19:26       ` Vitaly Fertman

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=1144059702.6316.62.camel@tribesman.namesys.com \
    --to=vs@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=sarathmenon@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.