Hammer error?

[Sdävtaker]

Oh, after retry with the new IP it started in
transactionid=000000000002 again, is it ok? shouldnt it start where it
crashed?
Sdav

On Wed, May 20, 2009 at 10:44, Sdävtaker <sdavtaker at gmail.com> wrote:
> I will check with the debugger later, but i can tell in advance that i
> found the trigger, i could reproduce the error :-)
>
> Machine0 has  standard out of the box hammerFS from installer, used
> for 2-3 months, now 30GB in /home, it's a server, it has a public
> static IP for his own.
> Machine1 fresh install same structure, running in a VM in my home
> behind a router, behind a ADSL (Dynamic-ip)
> I forwaded the ADSL port 22 to the Machine1, checked my ip address at
> the moment and ran:
>
> Machine0# hammer pfs-status /home   //to get shared-uuid
> Machine1# hammer pfs-slave /pfs/machine0.home shared-uuid=******
> Machine0# hammer mirror-copy /home root at Machine1IpAddress:/pfs/machine0.home
> It took a couple of hours (30GB) and sometime in the run the public
> address of my ADSL modem changed (not the internat, im still
> 192.168....)
> Then i got a hammer.core in my root's home.
> I think there is nothing to do about this just do the copy in small
> chunks, right?
> Sdav
>
> On Tue, May 19, 2009 at 22:49, Matthew Dillon
> <dillon at apollo.backplane.com> wrote:
>>
>> :Hello,
>> :I was doing some backup from Machine0 to Machine1 using hammer
>> :mirror-copy and got a suppicious new file called "hammer.core".
>> :Looking around the files it looks like a success copy but i still
>> :curious about this new 720kb file.
>> :Someone can tell me if i need to worry about it and where can i start
>> :checking for errors in case there was one?
>> :Machine0 has DFBSD2.2.0-release, Machine1 has DFBSD2.2.1-release,
>> :could it be the problem? should i just upgrade both?
>> :Sdav
>>
>>   A hammer.core could only come from the hammer utility core dumping.
>>   This wouldn't be a filesystem error but it certainly indicates a bug
>>   somewhere in the hammer utility.
>>
>>   If you haven't updated the sources relative to when the core was
>>   generated you can recompile the hammer utility with DEBUG_FLAGS=-g and
>>   then gdb the binary and core file and get a backtrace to see where it
>>   died.
>>
>>   If you have updated the sources since then you'd have to wait for a new
>>   core file to be generated for a newly debug-compiled hammer utility to
>>   match the core file.
>>
>>       cd /usr/src/sbin/hammer
>>       make clean
>>       make obj
>>       make DEBUG_FLAGS=-g all install
>>
>>       ...
>>
>>       gdb /sbin/hammer hammer.core
>>       ...
>>       gdb> back
>>
>>
>>                                        -Matt
>>                                        Matthew Dillon
>>                                        <dillon at backplane.com>
>>
>
>
>
> --
> Sdävtaker prays to Rikku goddess for a good treasure.
>



-- 
Sdävtaker prays to Rikku goddess for a good treasure.