[haiku-development] Re: Tracker Crash post-initialization (was: Filesystem corruption and Alpha-1)

  • From: David Himelright <david.himelright@xxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Tue, 23 Jun 2009 11:47:31 -0400

On Tue, Jun 23, 2009 at 9:10 AM, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:

>
> On 2009-06-23 at 15:00:01 [+0200], David Himelright
> <david.himelright@xxxxxxxxx> wrote:
> > On Tue, Jun 23, 2009 at 8:09 AM, Stephan Assmus <superstippi@xxxxxx>
> wrote:
> >
> > [...] I'll create a fresh image,
> > file a bug with a stack trace, and submit the shell script with the
> report
> > if it looks like it wasn't something entirely ideosyncratic about copying
> > from a vdi to a partition - or to this particular machine.
>
> That'd be great. Thanks!


I just managed to almost isolate the crash, managed to bring up gdb and then
realized that I hadn't loaded symbols at boot (may or may not be helpful,
first time looking at the output closely).

One question however: is there anything that I can do to provide canned
output for debugging of possible issues with the files themselves? I wasn't
able to reproduce with two disk images under virtualization, however the
copy from a VirtualBox vdi to a vmdk reference to a formatted partition on
disk produces the error just after initialization sometimes once, sometimes
a handful of times. This could be any number of things, it might be a
problem with the format of the files on disk, missing metadata, or simply
Tracker crashing due to unexpected latency due to the disk being marked busy
by another active partition.

Can anyone recommend a tool for investigating the possible filesystem issue
if the crash points in that direction? This smells like it might be a pain
to reproduce on another system.

~David

Other related posts: