Friday, September 21, 2018

Linux Error: Mount Point Doesn't Exists, Even Though Its There

You might encounter an error in Linux where one of the existing mount point or NFS share has abruptly gone (/mnt/orastore) and when you try to mount it, remount it, recreate the mount point directory or try to check current mounts from df command, you get some errors like below:

# df -kh
df: `/mnt/orastore': No such file or directory
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1              30G   12G   17G  40% /
tmpfs                  32G  704M   31G   3% /dev/shm
/dev/mapper/oradata-oracle
                       99G   73G   21G  78% /oracle
/dev/mapper/data_al-archive
                      197G   17G  170G   9% /archivelogs
rmannfs:/bkp_util/production/PLNPRD/
                       42T   14T   28T  34% /backup
rmannfs:/bkp_util/testdev/migrationbkp/
                       47T   20T   28T  42% /mig_backups
/dev/sr0              225M  225M     0 100% /mnt
# df -kh /mnt/orastore
df: `/mnt/orastore': No such file or directory
df: no file systems processed
# umount /mnt/orastore
umount.nfs: /mnt/orastore: not found
umount.nfs: /mnt/orastore: not found
# mount /mnt/orastore
mount.nfs: mount point /mnt/orastore does not exist
# mkdir -p /mnt/orastore
mkdir: cannot create directory `/mnt/orastore': Read-only file system


To sum it up it seems all confusing but if you observe carefully, one of the other mounts has (/mnt) has been done which is hiding the required mount point (/mnt/orastore) to be used for filesystem mount.

A simple solution to above issue is either to unmount (/mnt) and original mount (/mnt/orastore) should become accessible (at least on a re-mount).

The original mount can also be placed somewhere else but since it hasn't been cleanly unmounted, its recommended to follow above solution rather than possible other workarounds.

No comments:

Post a Comment