Strange HAMMER undo(1) behaviour
Hi,
I am seeing strange things with undo(1) printing "Warning: fake
transaction id ..." messages every now and then. Calling sync multiple
times, or waiting long periods of time does not change anything.
cd /hammer
echo "abc" > test
sync
undo -i test
Warning: fake transaction id 0x0000000100108220
Warning: fake transaction id 0x0000000102034230
Warning: fake transaction id 0x000000010203c2b0
Warning: fake transaction id 0x000000010208c460
Warning: fake transaction id 0x00000001020ac760
Warning: fake transaction id 0x0000000106f37f40
Warning: fake transaction id 0x0000000106f39fc0
Warning: fake transaction id 0x0000000106f67410
Warning: fake transaction id 0x0000000106f690b0
Warning: fake transaction id 0x0000000106f69bb0
Warning: fake transaction id 0x000000010a0a4660
Warning: fake transaction id 0x000000010dbb4530
Warning: fake transaction id 0x000000010dbb5350
Warning: fake transaction id 0x0000000113ad3e80
Warning: fake transaction id 0x0000000113ad3ea0
Warning: fake transaction id 0x0000000115b7b6b0
Warning: fake transaction id 0x0000000115b7bdf0
Warning: fake transaction id 0x0000000115b7d510
Warning: fake transaction id 0x0000000115b7d530
Warning: fake transaction id 0x0000000115b8ed70
Warning: fake transaction id 0x0000000115b8f0b0
Warning: fake transaction id 0x0000000115bd4350
Warning: fake transaction id 0x0000000115bd5950
Warning: fake transaction id 0x0000000115be7670
Warning: fake transaction id 0x0000000115be7690
Warning: fake transaction id 0x0000000115c3c270
Warning: fake transaction id 0x0000000115c5b570
Warning: fake transaction id 0x0000000115c5b590
Warning: fake transaction id 0x0000000115c5ba50
Warning: fake transaction id 0x0000000115dd7760
Warning: fake transaction id 0x0000000116035e20
Warning: fake transaction id 0x000000011629fdb0
Warning: fake transaction id 0x000000011629fdd0
Warning: fake transaction id 0x00000001162a0050
Warning: fake transaction id 0x00000001163366e0
Warning: fake transaction id 0x00000001163429b0
Warning: fake transaction id 0x0000000116343950
Warning: fake transaction id 0x0000000117c64260
Warning: fake transaction id 0x00000001287cc110
Warning: fake transaction id 0x00000001287cc130
Warning: fake transaction id 0x00000001287cc190
Warning: fake transaction id 0x00000001287cc1b0
Warning: fake transaction id 0x00000001287cc1d0
Warning: fake transaction id 0x00000001287cc1f0
Warning: fake transaction id 0x00000001287cc210
Warning: fake transaction id 0x00000001287cc230
Warning: fake transaction id 0x00000001287cc250
Warning: fake transaction id 0x00000001287ee2b0
Warning: fake transaction id 0x00000001287ee2d0
Warning: fake transaction id 0x00000001287ee2f0
Warning: fake transaction id 0x00000001287ee390
Warning: fake transaction id 0x00000001287ee3b0
Warning: fake transaction id 0x00000001287ee3d0
Warning: fake transaction id 0x00000001287ee9d0
test: ITERATE ENTIRE HISTORY
0x00000001287eea50 29-Sep-2010 15:13:58
But then sometimes, without changing the "test" file, it does not print
the "fake transaction id" messages. It is pretty random, where printing
it has a much higher probablity than not printing it!
# uname -a
root@kvmdragon:/etc# uname -a
DragonFly kvmdragon.ntecs.de 2.6-RELEASE DragonFly
v2.6.3.41.ge5a8b-RELEASE #3: Tue Aug 17 16:27:07 CEST 2010
root@kvmdragon.ntecs.de:/usr/obj/usr/src/sys/KVM i386
Is this normal? Also strange that for many files I do not have a
history, even so I haven't set nohistory on them. Other than that the
system is behaving normal. I had a power-failure issue last night, so I
can't say for sure if it is related to that.
Any hints to find out more?
Regards,
Michael
討論串 (同標題文章)