4 ms·
> Hard links mostly work as you tell them to. You may need to set things up properly, but it's essentially the same thing being done. That's bullshit. hard lin
by braindeath 7y ago
> Hard links mostly work as you tell them to. You may need to set things up properly, but it's essentially the same thing being done.
That's bullshit. hard links are the same exact inode, with all that entails. reflinking is at the data block level. Totally different.
- boomboomsubban 7y agoHow is linking based on file and linking based on block "totally different?"
- cmurf 7y agoHard links are essentially the filename that points to an inode. Creating a hard link creates just another filename associated with the same inode. Once a hard link, always a hard link, until destroyed. Reflink has its own fs metadata including inode, with (initially) shared extents. Those shared extents can have their blocks individually and independently modified, per file. The point at which there are no more shared blocks, they're not reflinks.
- im3w1l 7y agoIIUC: If you hard link two files, changing one file changes the other. If you dedupe two blocks, it will copy-on-write, meaning that changing one block does not change the other. It's not an intrinsic property of file-dedupe vs block-dedupe. It's just how it's conventionally done.
- braindeath 7y agohardlinks are paths pointing to the same inode - the same metadata, the same contents - they are the same file - just happen to have multiple addresses. Inodes that happen to share blocks are not the same file. ie totally different.