I modified /etc/fstab
.
I verified the new devices and I can mount them with the mount
command.
How may I validate the modifications made to /etc/fstab
?
Server Fault is a question and answer site for system and network administrators. It only takes a minute to sign up.
Sign up to join this communityYou can simple run: mount -a
-a Mount all filesystems (of the given types) mentioned in fstab.
This command will mount all (not-yet-mounted) filesystems mentioned in fstab and is used in system script startup during booting.
mount -a
by rereading /etc/fstab
would also reload /etc/mtab
so he should be fine with that only.
– Prix
Aug 26 '10 at 2:41
The mount command take an --fake
or -f
for short. The following command should do what you need:
mount -fav
The following is in the documentation for -f
option:
Causes everything to be done except for the actual system call; if it's not obvious, this ``fakes'' mounting the filesystem. This option is useful in conjunction with the -v flag to determine what the mount command is trying to do.
(Note this is Linux - check before using elsewhere: FreeBSD uses -f
for 'force' - exactly the opposite meaning.)
mount --fake -a
but it seems to return exit code($?)=0
always. Umm..
– kujiy
Oct 3 '18 at 11:54
successfully mounted
even when the mount point dosent exist
– DollarAkshay
Nov 23 '18 at 8:33
mount -fav
validated it as correct. As soon as I did a mount -a
it found an error.
– Adam Plocher
Aug 11 '19 at 20:42
sudo findmnt --verify --verbose
is the best way I've found
findmnt
told me that fuse.sshfs seems unsupported by the current kernel
, which is not true because I was able to mount the sshfs share with mount -a
– user84207
19 hours ago
I found this /problem/ but the solution didn't meet my requirements.
When rebooting with any invalid entries in the /etc/fstab, such as missing file systems that fsck cannot check; the system will fail to boot. That can be much more difficult to deal with if you have a headless box.
This is my solution to checking /etc/fstab to avoid this boot problem:
# cat /usr/local/bin/check-fstab-uuid-entries.sh
#!/usr/bin/env bash
for x in $(grep ^UUID /etc/fstab|cut -d \ -f 1|cut -d = -f 2)
do
if [ ! -h /dev/disk/by-uuid/$x ];then
echo $(grep $x /etc/fstab) ..... not found
fi
done
Note that if you add a swap file to your fstab, mount -a
won't turn it on: you'll want to run swapon -a
.
mount -a is safe method to check /etc/fstab otherwise wrong entry could break the system
It is also advised to keep a backup copy of original /etc/fstab file. it could be copied to home directory of root
TBH even fake mounting doesn't safely validate the fstab for bad fs type entries.
you can have entries that have correct uuid's, directories etc but if you specify a noexistant FS type this will halt your boot next time.
[root@grumpy ~]# grep backup /etc/fstab UUID=5ed48e5e-7251-4d49-a273-195cf0432a89 /mnt/backup noatime,nodiratime,xfs defaults,nodev,nosuid 0 0 [root@grump ~]# [root@grumpy ~]# mount -fav | grep backup /mnt/backup : successfully mounted [root@grumpy ~]#
I open another term or tab and run: tail -f /var/log/kern.log
Sometimes errors show there that don't show when mounting.