As configured the autofs module for ext2 filesystems will
try to run e2fsck on the filesystem before mounting and
will refuse to mount the filesystem if e2fsck returns an
However, the current e2fsck (from e2fsprogs-1.12-2) returns
an error if run on write-protected device. This means that
autofs will fail to mount write proteted floppies when
using a line line:
ext2-floppy -fstype=ext2 :/dev/fd0
but will quite happily do the right thing for:
dos-floppy -fstype=vfat :/dev/fd0
auto-floppy -fstype=auto :/dev/fd0
This last one, however is less than ideal because it fails
for DOS floppies and doesn't run fsck on ext2 floppies.
The fix would seem to be to check if the device is read-only
before invoking e2fsck, and using the -n option if it is.
Yes indeed, when a write-protected disk is attempted to be mounted
with autofs, one gets the error that the mount point does not exist.
Confirmed in test lab.
This bug has been assigned to a developer.
The two most recent comments (by jturner and dkl on 12/11/1998)
describe the bug as "VERIFIED" and then as "ASSIGNED". And yet
bugzilla shows a status of "RESOLVED". Why?
I've just verified that this bug is still present in RHL 6.0
(autofs-3.1.3-2 and e2fsprogs-1.14-4) so I'd not call that resolved.
Commit pushed to master at https://github.com/openshift/openshift-docs
Merge pull request #1068 from bfallonf/issue_385
GH issue #385: added para on logoutURL