cp dir ~/files/store/audio/@/
select * from objects where inode = 181
Please Log in or Create an account to join the conversation.
Fuco wrote: Yes, you are completely right! I've googled for "empty sha1 hash" and checked if there's something in the database with hash da39a3ee5e6b4b0d3255bfef95601890afd80709. One file showed up, probably from when I was just testing it and "touch"ing files, then tagging them. So that empty file killed the directories in the de-dupe process. The file also got all the tags from the directories, that's why it shows up in the /audio/@ listing.
$ mkdir ~/myfiles/store/tag/@/dir1
$ mkdir ~/myfiles/store/tag/@/dir2
$ cp /etc/issue ~/myfiles/store/tag/@/dir2
$ mkdir ~/myfiles/store/tag/@/dir3
$ fusermount -u ~/myfiles
$ ./src/tagsistant /tmp/test ~/myfiles
# [ ... usual Tagsistant output ... ]
$ ls -la ~/myfiles/store/tag/@
drwxr-xr-x 5 tx0 tx0 4,0K set 16 18:51 .
drwxr-xr-x 5 tx0 tx0 4,0K set 16 18:51 ..
drwxrwxr-x 2 tx0 tx0 4,0K set 16 18:51 dir
drwxrwxr-x 2 tx0 tx0 4,0K set 16 18:51 dir2
drwxrwxr-x 2 tx0 tx0 4,0K set 16 18:52 dir3
Fuco wrote: As a side-note, should the de-duplicated data be left in the archive or not? I've found both the directories in ~/.tagsistant/archive under their respective inode trees. So probably only files are actually removed from the archive.
Tagsistant is © Tx0 released under the GPL