Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 78738 - nodiratime option on ext3 fs causes kernel panic on boot
nodiratime option on ext3 fs causes kernel panic on boot
Product: Red Hat Linux
Classification: Retired
Component: mkinitrd (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Erik Troan
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2002-11-28 09:18 EST by Brian Morrison
Modified: 2007-04-18 12:48 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-14 15:53:01 EST
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 Brian Morrison 2002-11-28 09:18:29 EST
Description of Problem:

If the mount options specified for the root filesystem are 
rw,noatime,nodiratime in /etc/fstab, then despite rebuilding the initrd file 
for kernel 2.4.18-18.8.0 the system panics on boot complaining of a mount error 
22 and invalid mount option nodiratime.

This configuration works with other machines where ext3 is compiled into the 
kernel under RH 7.3

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

RH 8.0 plus all errata patches

How Reproducible:

Every time system booted in this state

Steps to Reproduce:
1. Change /etc/fstab / options to rw,noatime,nodiratime
2. Rebuild initrd in /boot
3. reboot system

Actual Results:

Kernel panic, unable to mount rootfs at all

Expected Results:

Normal boot expected!
Comment 1 Stephen Tweedie 2002-12-09 08:59:09 EST
The "nodiratime" option is not parsed by the kernel --- it is dealt with by the
user-space mount code.  The initrd uses a very restricted mount mechanism built
into the "nash" binary.  If you want nodiratime to work on an initrd, that needs
nash to understand the option.  Reassigning the bug.
Comment 2 Erik Troan 2003-01-14 15:53:01 EST
fixed in internal CVS -- this will make it into whatever mkinitrd is after 3.4.34

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