How do hard links affect deletion?

Hard links have a unique behavior when it comes to file deletion in a Linux file system. Here’s how they affect deletion:

Deletion Behavior of Hard Links

Shared Inode: Since hard links point to the same inode, deleting one hard link does not remove the actual file data from the disk. Instead, it only removes that specific link (name) to the inode.
Link Count: Each time you create a hard link, the link count for that inode increases. When you delete a hard link, the link count decreases. The file data remains on the disk as long as there is at least one hard link pointing to it.
Data Persistence: If you delete the original file (e.g., filea), and there are other hard links (like filec), the data will still exist and can be accessed through those remaining links. The file is only truly deleted when the link count reaches zero (i.e., when all hard links to that inode have been deleted).

Example Scenario

Consider the following scenario:

You create a file filea and a hard link filec to it:
```
echo "This is filea." > filea
ln filea filec
```
Check the link count:
```
ls -l filea filec
```
Delete filea:
```
rm filea
```
Check the contents of filec:
```
cat filec  # Output: This is filea.
```

In this case, even after deleting filea, filec still contains the original data because the inode is still referenced by filec.

Summary

Deleting a hard link only removes that specific name, not the actual data.
The file data remains accessible through other hard links until all links are deleted, at which point the inode and associated data are removed from the file system.

This behavior is crucial for data management, as it allows for safe file sharing and redundancy without immediate data loss upon deletion of a single link. If you have more questions or need further clarification, feel free to ask!