2010/9/30 Damian Lubosch <d...@xiqit.de>: > Hello! > > Is that something I should be alarmed of, or is it just a "debug" warning > message > > HAMMER: WARNING: Missing inode for dirent "pkgsrc" > obj_id = 00000001040faf6f, asof=0000000106dda770, lo=00030000 > HAMMER: WARNING: Missing inode for dirent "pkgsrc" > obj_id = 00000001040faf6f, asof=0000000106dda770, lo=00030000 > HAMMER: WARNING: Missing inode for dirent "pkgsrc" > obj_id = 00000001040faf6f, asof=0000000106dda770, lo=00030000 > HAMMER: WARNING: Missing inode for dirent "pkgsrc" > obj_id = 00000001040faf6f, asof=0000000106dda770, lo=00030000 > HAMMER: WARNING: Missing inode for dirent "ld-elf.so.2" > obj_id = 0000000105f776df, asof=0000000106dda770, lo=00030000 > HAMMER: WARNING: Missing inode for dirent "ld-elf.so.2" > > I deleted some files few days ago, and now my dmesg.today and .yesterday is > full of those messages. > > I am using DFly 2.6.3 amd64 with a patched twa(4) driver for hardware raid. > [...]
See undo(1) under the 'DIAGNOSTICS' section: http://leaf.dragonflybsd.org/cgi/web-man?command=undo§ion=ANY Warning: fake transaction id 0x... While locating past versions of the file, undo came across a fake transaction id, which are automatically generated by hammer(5) in case the file's directory entry and inode got bisected in the past. Matt, could we just silence this warning, if it isn't important any more ? This has been a recurring source of confusion. Best regards, Stathis
