Ultra console automounter fails to mount data drive if maximum mounts has been reached

Create issue
Issue #1 resolved
Jeremy Gill repo owner created an issue

Seen yesterday at RRI:

RRI uses a 1.5 TB external RAID array as their primary storage device. The device used to be mounted at boot time with an entry in /etc/fstab. The problem is that if the device is powered off during the boot, Linux will halt the boot and dump the user into a Ctrl+D environment to 'fix' the missing drive problem. This is undesirable in this case because end-users don't know what to do. Switching this to using an automounter also had an undesireable effect, however: The filesystem is an ext3 type fs and keeps track of mount count between fscks. The max number allowed had been hit, and the automounter appears to stall in this case.

The work-around is simple: run fsck on the drive, but is there a better way?

Comments (2)

  1. Jeremy Gill reporter

    Solution:

    1. adjust /etc/auto.master to ensure /vol mounts don't time out -/vol /etc/auto.vol --timeout=2 +/vol /etc/auto.vol --timeout=0

    2. for good measure, use tune2fs to disable automatic fscks

  2. Log in to comment