Re: tob problems

[Jim Pick <jim@jimpick.com>]

Johann Spies <jhspies@alpha.futurenet.co.za> writes:

> I have used tob before, but today I get a segmentation fault every time I
> want to do a -fullcount of -full backup.
> 
> It ends like this:
> -------------------------------------------------------------
> current->tss.cr3 = 00641000, %cr3 = 00641000
> *pde = 00000000
> Oops: 0002
> CPU:    0
> EIP:    0010:[<0011e00a>]
> EFLAGS: 00010207
> eax: 00000636   ebx: 00000636   ecx: 0000018d   edx: 016e1000
> esi: 016e1000   edi: 400ca000   ebp: 0024c5b4   esp: 01500f54
> ds: 0018   es: 002b   fs: 002b   gs: 002b   ss: 0018
> Process find (pid: 211, process nr: 19, stackpage=01500000)
> Stack: 00000018 00000000 014326a4 00001000 0178cb00 0011bf91 00000000
> 00000000
>        00000000 00000000 00000001 00000001 00000000 00000000 00000000
> 00000000
>        001252ec 0178cb00 014326a4 400ca000 00001000 01528810 0805aee0
> 08056cd0
> Call Trace: [<0011bf91>] [<001252ec>] [<0010abe9>]
> Code: f3 a5 83 e3 03 89 d9 f3 a4 07 55 89 44 24 14 e8 92 39 00 00
> /sbin/tob: line 193:   211 Segmentation fault      $nicefindcmd find `cat

That is a kernel oops.

It's not terribly useful on it's own - unless you supply more
information along with it.  Read:

  http://www.tux.org/lkml/   (read the part about oops)
  Documentation/oops-tracing.txt   in the kernel sources

It's a kernel thing - so there might be a problem with the driver you
are using...

Cheers,

 - Jim