My fault … that’s my pcmanfm PPA, not my pcmanfm-testing PPA
So you don’t have the one I’m testing for released on that machine … not Chloes PC then 
not Chloes PC then :)
No this is my PC
Could this issue be caused because Timeshift uses hard links ?
Graeme
Could be yes … if it’s using hard links to files outside the /timeshift directory those will be included in the directory size because as far as the filesystem is concerned they actually exist inside that directory.
Soft links would not be followed, and just the size of the symlink would be counted.
From what I understand Hard Links are used to save space and I’ve read about it on a wiki over and over and I kinda semi understand the concept but I can’t get my head completely around it and how it applies to my problem but something tells me hard links have something to do with it and pcmanfm and thunar are both being fooled by them.
So what I plan to do is format a 40gb external usb drive I have to store the snapshots that way I have something of a known size to work with
Graeme
OK a “soft” link is a file that points to the path of another (target) file … ie. move/rename the target it point to and the link will be broken because the path of the target has changed
a “hard” link is a reference to the inode of the target so it effectively is the target … move/rename the target and the link will still work as the link is following the files inode and that will have stayed the same.
One is working at the “file” level, and the other is working at the inode level … so a soft link is a file that says “go to this target file /path/to target”, where a hard link says “I AM the target file inode 200”
(if 200 is the targets inode)
soft link, points to the target by it’s path in the mounted filesystem
hard link reference the target by it’s physical location on the disk
Make sense ?
–