wrong inode number reported

[michael-ts]

I copied a file "test.txt" to ~/myfiles/store/A. Then I copied it from there to ~/myfiles/store/B. Then I ran find ~/.tagsistant/archive and saw a single instance of the file named "archive/9/1/19___test.txt". But when I run ls -li store/A/@/test.txt store/B/@/test.txt I get:

41 -rw-rw-r-- 1 michael michael 62762 Nov  6 21:14 A/@/test.txt
42 -rw-rw-r-- 1 michael michael 62762 Nov  6 21:14 B/@/test.txt

First of all, the two inode number don't match (41 != 42), even though they are both represented by the same underlying Tagsistant inode number. Second, neither of them actually even match the underlying inode number used by Tagsistant, which is 19. 41 != 42 != 19.

[StrumentiResistenti]

I should check the reason why the inode is forged instead of taking the internal id used inside archive/. Maybe I've done this to fulfil some POSIX semantics requirement I'm currently unable to spot. Even POSIX allows two paths sharing the same inode, using hard links.

Is this a blocking behaviour?

[michael-ts]

@StrumentiResistenti No, not blocking.