linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12354] New: Advisory: Debian's current initramdisk scripts break with an ext4 root
Date: Sat,  3 Jan 2009 23:02:15 -0800 (PST)	[thread overview]
Message-ID: <bug-12354-13602@http.bugzilla.kernel.org/> (raw)

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

           Summary: Advisory: Debian's current initramdisk scripts break
                    with an ext4 root
           Product: File System
           Version: 2.5
     KernelVersion: 2.6.28
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: enhancement
          Priority: P1
         Component: ext4
        AssignedTo: fs_ext4@kernel-bugs.osdl.org
        ReportedBy: jimsantelmo@gmail.com


This is just a heads-up to hopefully save other people some time. I'm running
2.6.28 with debian/unstable, finally converted the root to ext4, and discovered
that Debian with an initrd can't boot it because the initrd scripts apparently
decide it is an ext3 filesystem with unsupported features. Not that they report
this: instead you get an ENODEV message that had me convinced ext4 wasn't
registering itself or some other such weirdness. Works fine if you use a
"rootfstype=ext4" kernel boot parameter, or no initrd.


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

             reply	other threads:[~2009-01-04  7:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-04  7:02 bugme-daemon [this message]
2009-01-04 18:14 ` [Bug 12354] Advisory: Debian's current initramdisk scripts break with an ext4 root bugme-daemon
2009-01-04 19:14 ` bugme-daemon
2009-01-04 19:16 ` bugme-daemon
2009-01-04 19:30 ` bugme-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-12354-13602@http.bugzilla.kernel.org/ \
    --to=bugme-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).