Linux mount same partition to 2 paths

------------------------------------
Use a Bind Mount: A bind mount allows you to mount an already mounted filesystem at a new location. This does not require the device to be unmounted.

To perform a bind mount, you can use the following command:

sudo mount --bind /mnt/sda3 /mnt/sdk3

After this command, both /mnt/sda3 and /mnt/sdk3 will point to the same filesystem, and changes made in either will be reflected in both locations.

------------------------------------


------------------------------------
#!/bin/bash

# Label of the partition to search for
PARTITION_LABEL="wd1TBd_ext2"

# Mount point for the bind mount
MOUNT_POINT="/mnt/sdk3"

# Find the partition by its label
DEVICE=$(lsblk -o NAME,LABEL | grep "$PARTITION_LABEL" | awk '{print $1}')

if [ -z "$DEVICE" ]; then
    echo "Partition with label '$PARTITION_LABEL' not found."
    exit 1
fi

# Get the full device name (e.g., /dev/sda1)
DEVICE="/dev/$DEVICE"

# Check if the partition is mounted
if mount | grep "on $MOUNT_POINT " > /dev/null; then
    echo "$MOUNT_POINT is already mounted."
    exit 0
fi

# Create the mount point if it does not exist
if [ ! -d "$MOUNT_POINT" ]; then
    echo "Creating mount point '$MOUNT_POINT'."
    mkdir -p "$MOUNT_POINT"
fi

# Bind mount the partition to the mount point
mount --bind "$DEVICE" "$MOUNT_POINT"

# Check if the bind mount was successful
if [ $? -eq 0 ]; then
    echo "Successfully bind mounted '$DEVICE' to '$MOUNT_POINT'."
else
    echo "Failed to bind mount '$DEVICE' to '$MOUNT_POINT'."
    exit 1
fi


------------------------------------

A bind mount and a hard link are related concepts in file systems, but they serve different purposes and have distinct behaviors. Let's break down the differences and discuss their advantages and potential problems:

### Bind Mount
A bind mount allows you to mount an existing directory (or file) to another location in the file system. This means that the same underlying data can be accessed from multiple paths. It is created using the `mount` command in Linux.

**Example:**
```bash
mount --bind /mnt/sda3 /mnt/sdk3
```

**Characteristics:**
- Both the original mount point (`/mnt/sda3`) and the bind mount (`/mnt/sdk3`) refer to the same inode (the internal representation of the file or directory in the filesystem).
- Changes made in one location are immediately reflected in the other.
- Unmounting the bind mount does not affect the original location.
- This can be useful for organizing file systems or making certain locations accessible at different paths.

### Hard Link
A hard link creates an additional directory entry for an existing file. Unlike a bind mount, a hard link does not involve the filesystem mount system; it is purely a file system operation. You create a hard link using the `ln` command without the `-s` option.

**Example:**
```bash
ln /mnt/sda3/file.txt /mnt/sdk3/file.txt
```

**Characteristics:**
- A hard link points to the same inode as the original file. Such links share the same file data.
- Files must reside on the same filesystem for hard links.
- Both links are indistinguishable; deleting either one does not delete the actual data until all links to it are removed.
- Hard linking can only be done on files, not on directories, except by the root user under specific circumstances.

### Symbolic Link vs Hard Link
Note that in your example, you've used `ln -s`, which creates a symbolic (soft) link instead of a hard link. Here's a brief look at symbolic links:

- A symbolic link points to the path of the target file or directory and can link across different filesystems.
- If the target file is deleted, the symbolic link becomes broken (dangling).

### Advantages and Problems

#### Bind Mounts
**Advantages:**
- Can mount entire directories to another location in the file system.
- Works even across different directories (unlike hard links).
- Useful for various administrative tasks or for creating a uniform directory structure.

**Problems:**
- Unmounting can be overlooked, as it doesn't affect the original mount.
- May complicate the filesystem hierarchy if not managed properly.

#### Hard Links
**Advantages:**
- Can help save space by avoiding data duplication.
- The actual data only gets deleted once the last link is removed (data integrity).

**Problems:**
- Cannot span across different filesystems.
- Not applicable to directories (except in special cases).
- Can create confusion, as you may have multiple directory entries pointing to the same data, making tracking harder.

### Summary
- Use **bind mounts** when you want to refer to the same directory (or file) at multiple paths in the same filesystem.
- Use **hard links** when you want to create multiple directory entries for the same file within the same filesystem.
- If you meant to compare bind mounts to symbolic links, remember that symbolic links can point to files across different filesystems, while bind mounts cannot.