Bug 540126 - data=ordered instead of what is in fstab
data=ordered instead of what is in fstab
Product: Fedora
Classification: Fedora
Component: grubby (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Peter Jones
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-11-22 08:57 EST by Laurent Jacquot
Modified: 2010-12-03 21:59 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-12-03 21:59:15 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 Laurent Jacquot 2009-11-22 08:57:18 EST
dracut doen't keep the data options from fstab when building initramfs, preventing a successfull switchroot later on

/boot on raid1
/ on lvm-on-raid5
F12 freshly preupgraded from f11

cat /etc/fstab | grep " / "
UUID=XXX /  ext3 defaults,noatime,data=writeback 1 1

How reproducible:
every time, if data=writeback is skipped and initramfs recreated, everything is working

This is not a high priority bug (data is not changing a lot on /), but it can prevent a newbye following random advice on internet (like data=writeback) from using f12
Comment 1 Harald Hoyer 2009-11-23 03:54:03 EST
add "rootflags=noatime,data=writeback" to the kernel command line
Comment 2 Harald Hoyer 2009-11-23 05:27:32 EST
for "new-kernel-pkg", please consider adding rootflags="" to the kernel command line for special options in fstab
Comment 3 Laurent Jacquot 2009-11-25 08:26:19 EST
Thanks for the tip,
But I feel this should be handled more automagically like it has always been: why not include these options at initramfs build time?
rootflags could then be used to override if needed...

Whatever, WONTFIX or NOTABUG is also fine with me..
Comment 4 Bug Zapper 2010-11-04 01:44:39 EDT
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 5 Bug Zapper 2010-12-03 21:59:15 EST
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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