Red Hat Bugzilla – Full Text Bug Listing
|Summary:||[PATCH] RFE: ext4 support in grub|
|Product:||[Fedora] Fedora||Reporter:||David Nielsen <gnomeuser>|
|Component:||grub||Assignee:||Peter Jones <pjones>|
|Status:||CLOSED RAWHIDE||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||rawhide||CC:||alexandre.magaz, ascii79, atigro, atorkhov, awilliam, ben, dcantrell, ddumas, esandeen, itamar, john.haxby, joshuacov, kas, kevin, lex.lists, martin, mishu, nsoranzo, peter, pjones, redhat-bugzilla, ronny.fischer, sesh, vaurora, wade.nels, wtogami|
|Target Milestone:||---||Keywords:||Patch, Reopened|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2009-08-06 18:06:44 EDT||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
|Bug Blocks:||473303, 507676|
Description David Nielsen 2009-02-19 02:29:50 EST
Description of problem: As ext4 is now the default filesystem, it would be the nicest solution if /boot was also capable of using this. A patch can be found below taken from the Ubuntu grub package to add this capability: http://launchpadlibrarian.net/20944879/grub_ext4.diff
Comment 1 lexual 2009-03-01 04:30:50 EST
Just converted my /boot to ext4, and rebooted fine.
Comment 2 lexual 2009-03-01 04:50:42 EST
*** Bug 446276 has been marked as a duplicate of this bug. ***
Comment 3 Peter Gordon 2009-03-01 15:17:56 EST
(In reply to comment #1) > Just converted my /boot to ext4, and rebooted fine. How did you accomplish this? If it was by a simple remounting as ext4, then the file on-disk is still using the ext3-format bitmap, and not the ext4-style extents. It is this on-disk extent support which GRUB cannot handle at this time, and what the proposed patch accomplishes. When remounting an ext3 filesystem as ext4, only newly-created files use this extent support.
Comment 4 David Nielsen 2009-03-01 15:40:15 EST
For reference, I have succesfully installed a Ubuntu Jaunty Alpha 5 on full ext4 setup. This is the very patch they use to provide this functionality.
Comment 5 lexual 2009-03-01 16:50:26 EST
Steps taken: tune2fs -O extents,uninit_bg,dir_index /dev/DEV fsck -pf /dev/DEV edited fstab.
Comment 6 Peter Gordon 2009-03-02 02:32:36 EST
(In reply to comment #5) > Steps taken: > > tune2fs -O extents,uninit_bg,dir_index /dev/DEV > > fsck -pf /dev/DEV > > edited fstab. According to the e2fsck manual page, this only forcibly repairs the filesystem; but does not change it if it is already intact. In order to verify that ext4 (extents) support is functional, you would need to recreate the necessary files in /boot with extents enabled. For example, copy - not move - the files and rename them to replace the old ones. If you do this you will likely not be able to boot without this patch in Grub. (I for one, have had quite difficulty with this in my rawhide VM.)
Comment 7 Eric Sandeen 2009-03-31 10:44:05 EDT
Created attachment 337317 [details] proposed patch Here's the patch from the Google SoC project, also an srpm at http://sandeen.fedorapeople.org/grub-0.97-43.fc11.ext4.src.rpm for anyone who would like to test it. Thanks, -Eric
Comment 8 Arkady L. Shane 2009-04-01 13:48:36 EDT
It work, but I have to patch anaconda to enable boot from ext4.
Comment 9 Joshua Covington 2009-04-11 17:45:55 EDT
Is there any hope that is merged in rawhide? What will happen when all the new users install f11 with ext4 as default and grub not supporting it? Maybe this is not the most important issue but will be a problem.
Comment 10 Eric Sandeen 2009-04-11 17:56:42 EDT
It may hit rawhide but unlikely to hit F11. It should not be a problem; it does require a separate non-ext4 /boot, but you get separate /boot by default anyway with a default lvm install... It would have been great to get this in around alpha, but there were other more pressing matters and it didn't happen. The only minor annoyance is the requirement for separate /boot even when you aren't using lvm for /. It's not great, but we can live with it I think. Thanks, -Eric
Comment 11 Arkady L. Shane 2009-04-18 16:20:51 EDT
And what you think about this. Anaconda by default does not allow to boot from ext4. So maybe it is possible to include this patch to grub? Manually people could install grub onto ext4 but they could not do it during installation.
Comment 12 Eric Sandeen 2009-04-18 16:25:22 EDT
It's too late for this for F11, but we can put it into rawhide now (or soon) for testing.
Comment 13 Wade Nelson 2009-04-25 15:14:49 EDT
I feel this should be on the short list of things that need to be fixed before F11 release. The following problem arises: * F11 cannot boot ext4 filesystems. * The F11 Live media will only install with / formatted ext4. * There is no way to install the Fedora 11 live media without using LVM or having a separate boot. The only way to install Fedora 11 without LVM or a separate /boot is to use the DVD and select ext3. I've got nothing against ext3, but I was hoping to not have to download the full DVD to do a basic install. I'm sure there are many people who do not use LVM, and do not have a separate /boot. Doesn't seem like a very well thought out approach to ext4 adoption to me.
Comment 14 Eric Sandeen 2009-04-25 17:18:24 EDT
See comment #12; it's too late for F11; it's somewhat unfortunate I agree, but other things took priority. An ext4-capable grub should be in rawhide reasonably soon I hope; if you feel very strongly about not having a separate /boot, put it at the end of your disk for now, upgrade grub when ext4 capability is done, move /boot onto the root, and lose the separate partition... it's not pretty, but you can get there.
Comment 15 Kevin Kofler 2009-04-28 18:06:07 EDT
How is it too late? There are still a few days left for late tagging for critical issues like this.
Comment 16 David Nielsen 2009-04-28 18:58:42 EDT
If the concern is stability, the patch I attached when I reported this months ago is the same that ships in Ubuntus latest release. They have not had any bugs in that time using this and there are thousands of people using it every day. That is months of testing and one very large scale deployment.
Comment 17 Eric Sandeen 2009-04-28 22:16:08 EDT
David, I have no idea how many people are actually installing Jaunty on ext4, and based on the approximately 0 patches contributed from Ubuntu devs to either ext4 kernelspace or userspace, you'll have to forgive my not accepting "But it's in Jaunty!" as sufficient reason to merge it now. Guys I am really sorry this didn't make it, but - it didn't make it. I expect we'll have a grub update at some point in F11 if people just can't stand their ext3 /boot and absolutely must migrate off it. David, I do appreciate your tracking down the Debian patch Ubuntu is using. I regret that I didn't get it vetted in time to feel confident about merging it, but fixing things like corruptions and oopses and fsck failures came before a native ext4 /boot. -Eric
Comment 18 Joshua Covington 2009-05-06 16:17:57 EDT
I do appreciate your efforts in fixing corruptions and oopses and fsck failure etc. But why I need LVM with just 1 HDD? Can you please add the patch at least in koji (or somewhere else)? For those who "don't like" f11 with separete /boot as ext3: 1. rebuild grub from http://sandeen.fedorapeople.org/grub-0.97-43.fc11.ext4.src.rpm 2. you can also aply the patch to more recent grub build from koji. 3. respin the install dvd and put the new grub.rpm in it. 4. install It's not perfect but it's a lot better than waisting 1 partition (from 4) just because of this. I hope we can see a better solution about this.
Comment 19 David Nielsen 2009-05-31 04:27:55 EDT
F12 has been open for a while, can we pleased get this patch applied so that the feature can get the desired testing?
Comment 20 Valerie Aurora Henson 2009-06-29 16:49:49 EDT
I reviewed both the version of the grub patch Eric proposed (attached to this bug report) and the most recent Debian version. Eric's preferred version is cleaner and more correct and looks good to me, modulo one spelling error he will fix shortly. :) Ship it!
Comment 21 Peter Jones 2009-06-30 10:59:21 EDT
This patch is applied in grub-0.97-52 .
Comment 22 Itamar Reis Peixoto 2009-06-30 11:08:20 EDT
(In reply to comment #21) :-) anaconda need to be changed to support ext4 /boot in F12.
Comment 23 Kevin Kofler 2009-06-30 11:12:03 EDT
There should also be a grouped grub,anaconda update for F11 for respins to pick up.
Comment 24 Eric Sandeen 2009-06-30 11:21:07 EDT
(In reply to comment #23) > There should also be a grouped grub,anaconda update for F11 for respins to pick > up. Let's test it in rawhide just a bit first ;)
Comment 25 Adam Williamson 2009-07-15 12:34:08 EDT
We're coming up on F12 alpha release, it'd be very nice to have this in there. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Comment 26 Eric Sandeen 2009-07-15 12:39:25 EDT
(In reply to comment #25) > We're coming up on F12 alpha release, it'd be very nice to have this in there. And indeed, you might notice that the bug is in MODIFIED state; it's in there. ;)
Comment 27 Adam Williamson 2009-07-15 13:19:44 EDT
I assumed it had been set to MODIFIED when the grub patch went in, given the discussion above. Happy to be wrong. =) So we just need someone to confirm they can do an install of Rawhide with /boot on an ext4 partition in order to close this... -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Comment 28 Eric Sandeen 2009-07-15 13:22:21 EDT
Well, this was just the grub bug. Anaconda needed a change too, I dunno if it had a bug open. But this bug went to MODIFIED when grub got the ext4 patch committed. -Eric
Comment 29 Jeremy Katz 2009-07-15 14:38:16 EDT
And the anaconda patch went in right after (just via IRC, not via an explicit bug)
Comment 30 Adam Williamson 2009-07-17 13:27:50 EDT
Setting this as blocking f12alpha (we want to confirm it's working for the alpha release). -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Comment 31 Denise Dumas 2009-07-17 13:51:25 EDT
grub and anaconda are both changed. we may, at some point, want to change /policy/ on when we use what by default in anaconda, but support for using it is all there. ext4 by default on everything but /boot is what's currently there. ext4 can be used but is not default. If someone wants to confirm they can do an install of Rawhide with /boot on an ext4 partition we can close this out.
Comment 32 Denise Dumas 2009-07-17 14:06:28 EDT
update: looks like the default was changed a short time ago as well.
Comment 33 Jesse Keating 2009-08-06 18:06:44 EDT
As of 20090806 the default is still ext3 for /boot. However I forced my /boot to be ext4 and the system booted fine. Closing this bug.
Comment 34 firstname.lastname@example.org 2015-10-02 07:21:32 EDT
For what it's worth, there is a *very* longstanding bug in grub (not grub2) that means that reading files with a few (ext4) extents is incredibly slow. On the bare-metal system I tested, a boot with an initramfs with just one extent took less than two seconds to load the kernel and initramfs. On the same system, and initramfs with seven extents (as reported by filefrag) took 24s to load. On other systems -- and especially virtual machines -- the difference is between a few seconds and several *minutes*. grub2 doesn't have the same problem so this (and its fix) are mainly of historic interest although it does still apply to RHEL6/CentOS6/OL6, of course.
Comment 35 Eric Sandeen 2015-10-02 09:04:03 EDT
Hi John, has that bug been filed or triaged anywhere? More details?
Comment 36 email@example.com 2015-10-02 09:07:48 EDT
Not yet ...