Bug 61009 - vfat entries in fstab cause system to hang on boot
vfat entries in fstab cause system to hang on boot
Product: Red Hat Linux
Classification: Retired
Component: autofs (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeffrey Moyer
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2002-03-11 16:54 EST by Need Real Name
Modified: 2007-04-18 12:40 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-10-21 11:11:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2002-03-11 16:54:14 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.9-21custom i686)

Description of problem:
non auto-mounting entriess for local vfat filesystems declared in /etc/fstab
cause boot to multi-user to hang.
Compiling Vfat/DOS drivers static in kernel does not solve.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Create Vfat partitions. Format. Mount and test.
Add entries to /etc/fstab with options to no-auto mount: (and mounts points ;-)

/dev/hda1              /dos/c          vfat    noauto,rw       0 0


Actual Results:  System hangs on boot

Expected Results:  Same entries in 6.2 and 7.0 worked ok
I used auto.mount tables to mount/umount on demand.

Additional info:

Tried compiling MSDOS and VFAT into static kernel so that dvrs would be avail
from boot. No joy.
Comment 1 Michael Schwendt 2002-04-19 07:56:10 EDT
1. When exactly does the boot procedure hang?

2. Are you sure you have "0 0" at the end of the line in /etc/fstab?
Comment 2 Jeffrey Moyer 2004-03-19 17:45:21 EST
Please answer the above questions.

Comment 3 Jeffrey Moyer 2005-10-21 11:11:57 EDT
closing bug due to inactivity.

Note You need to log in before you can comment on or make changes to this bug.