Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 82229

Summary: non existent label mounts even with the 'noauto' option cause boot time drop to emergency shell
Product: [Retired] Red Hat Linux Reporter: Matthew Galgoci <mgalgoci>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED DEFERRED QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-09-29 20:34:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 79579, 100644    

Description Matthew Galgoci 2003-01-20 04:50:47 UTC
Description of problem:

I have a removable disk drive that I want to mount using a filesystem label.

The drive contains an ext3 filesystem labeled as /mnt/shemp

/mnt/shemp exists

I also have the following entry in /etc/fstab:

LABEL=/mnt/shemp   /mnt/shemp              ext3    noauto        1 1

Upon rebooting without /mnt/shep available in the system, I am dropped to 
a filesystem repair shell (of course first prompting for the root password).

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

initscripts-7.04-1

How reproducible:

Every time.

Steps to Reproduce:
1. Add a non-existent label mount to /etc/fstab with the noauto option
2. reboot
3. watch it prompt you for your root password and to fix your filesystem
    
Actual results:

You are prompted to fix the filesystem

Expected results:

The non-existent label with the noauto option should simply be ignored since 
you are not going to mount the filesystem automagically anyhow.

Comment 1 Bill Nottingham 2003-01-20 20:40:15 UTC
Did this happen previously?

Comment 2 Matthew Galgoci 2003-01-20 21:07:03 UTC
I could have sworn it worked before, but I just tried on an advanced server
2.1 with all current updates and it indeed failed.

However, on a hunch I changed the fs_freq and fs_passno fields both to 0 and 
the system booted without complaint. Weird.

Is it semantically correct behaviour? 

I will test the beta4 box again tonight when I get home to ensure that the same
behaviour holds.

Comment 3 Bill Nottingham 2005-09-29 20:34:56 UTC
Closing bugs on older, no longer supported, releases. Apologies for any lack of
response.

If this persists on a current release, such as Fedora Core 4, please open a new bug.