linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 13992] New: ext3 data=ordered in fstab prevents booting
Date: Sun, 16 Aug 2009 00:46:13 GMT	[thread overview]
Message-ID: <bug-13992-13602@http.bugzilla.kernel.org/> (raw)

http://bugzilla.kernel.org/show_bug.cgi?id=13992

           Summary: ext3 data=ordered in fstab prevents booting
           Product: File System
           Version: 2.5
    Kernel Version: 2.6.30.4
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext3
        AssignedTo: fs_ext3@kernel-bugs.osdl.org
        ReportedBy: rogerx@sdf.lonestar.org
        Regression: No


I ran into a problem when, when setting CONFIG_EXT3_DEFAULTS_TO_ORDERED=n, the
system will not complete booting when data=ordered is set on the root
filesystem within /etc/fstab.

(Can't remember the exact debug output as I've been muddling over possible
e100.c system freezes.)


Some work quick hacks that may help resolve are, fsck the filesystem and
removing the filesystem option from the /etc/fstab file.


This will likely occur with people upgrading from 2.6.29 to 2.6.30 with the
data=ordered filesystem option set in fstab.

(I personally like a more stable filesystem, so I've set
CONFIG_EXT3_DEFAULTS_TO_ORDERED=y due a more severe bug I was tracking down in
2.6.30 concerning e100.c)

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

             reply	other threads:[~2009-08-16  0:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-16  0:46 bugzilla-daemon [this message]
2009-08-19 12:47 ` [Bug 13992] ext3 data=ordered in fstab prevents booting bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-13992-13602@http.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).