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
:Oh, after retry with the new IP it started in
:transactionid=3D0002 again, is it ok? shouldnt it start where it
:crashed?
:Sdav
This isn't a bug but it is a missing feature. What is happening is
that the mirror stream is trying to eat too large a chunk (the entire
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
Sdävtaker 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
: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
