Added a comment

This commit is contained in:
jgoerzen 2022-09-19 13:55:07 +00:00 committed by admin
parent 00418e8c8f
commit d3408ec63d

View file

@ -0,0 +1,47 @@
[[!comment format=mdwn
username="jgoerzen"
avatar="http://cdn.libravatar.org/avatar/090740822c9dcdb39ffe506b890981b4"
subject="comment 4"
date="2022-09-19T13:55:07Z"
content="""
Examining that `git show` command:
```
git show git-annex:$(git-annex examinekey SHA256E-s55936559--0d418e4bb62cfc7ef5b053f8b622dd72794781a49931abc41bb9499acaf51b09.mp4 --format='${hashdirlower}${key}.log.cid')
1662351509.054973915s 58255588-b988-47ba-9a88-7cb1118503ba 164140 55936559 1585707132 :167232 55936559 1585707132
```
From the source material:
```
$ stat '0_New/5/20-03-31 21-12-12 0184.mp4'
File: 0_New/5/20-03-31 21-12-12 0184.mp4
Size: 55936559 Blocks: 109238 IO Block: 131072 regular file
Device: 49h/73d Inode: 167232 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 1000/jgoerzen) Gid: ( 1000/jgoerzen)
Access: 2020-03-31 21:12:12.000000000 -0500
Modify: 2020-03-31 21:12:12.000000000 -0500
Change: 2020-06-07 23:07:21.475946002 -0500
Birth: -
```
So it looks like the inode number changed. But, on a hunch, I thought: this only happens with duplicate files; what if there's a file with that sha256 and that inode number?
And sure enough:
```
stat ./0_New/5/laura-john-20200331.mp4
File: ./0_New/5/laura-john-20200331.mp4
Size: 55936559 Blocks: 109238 IO Block: 131072 regular file
Device: 49h/73d Inode: 164140 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 1000/jgoerzen) Gid: ( 1000/jgoerzen)
Access: 2020-03-31 21:12:12.000000000 -0500
Modify: 2020-03-31 21:12:12.000000000 -0500
Change: 2020-03-31 21:21:50.131297383 -0500
Birth: -
```
I didn't set ignoreinodes on this remote.
Is that helpful?
"""]]