Bug 124110 - autofs fails to mount ext3 filesystems
Summary: autofs fails to mount ext3 filesystems
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: autofs
Version: 2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Moyer
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-05-24 06:28 UTC by Julian C. Dunn
Modified: 2007-11-30 22:10 UTC (History)
2 users (show)

Fixed In Version: autofs
Clone Of:
Environment:
Last Closed: 2005-08-20 06:22:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Julian C. Dunn 2004-05-24 06:28:37 UTC
Description of problem:

The autofs automounter cannot mount ext3 filesystems. It claims
"filesystem needs repair, won't mount" even when the filesystem is clean.

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

autofs-4.1.2-2

How reproducible:

Attempt to mount an ext3 filesystem which is mapped in an autofs map.
It will fail. An iso9660 filesystem works (i.e. a CD).

Steps to Reproduce:
1. Add a line like this to /etc/auto.master:

/local          /etc/auto.local --timeout 60

2. In /etc/auto.local, have a line like this:

l1      -fstype=ext3,rw :/dev/hda2

3. Make sure /dev/hda2 is clean by running fsck manually. Now try to
trigger automounting by changing to /local/l1.
  
Actual results:

May 24 02:17:52 XXXXX automount[29612]: mount(ext2): /dev/hda2:
filesystem needs repair, won't mount
May 24 02:17:52 XXXXX automount[29612]: failed to mount /local/l1

Expected results:

  Filesystem is mounted.

Additional info:

Comment 1 Jeff Moyer 2004-05-24 14:41:55 UTC
Try autofs-4.1.2-6 from:
  http://people.redhat.com/~jmoyer/

-Jeff

Comment 2 Julian C. Dunn 2004-05-24 15:10:21 UTC
Excellent, that worked. Thanks!

Comment 3 Matthew Miller 2004-09-19 16:31:05 UTC
Can this be pushed out as a fix, then? Thanks.

Comment 4 Marius Andreiana 2005-08-20 06:22:46 UTC
FC4 has version autofs 4.1.4. FC2 is no longer supported


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