All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marvin <marvin24@gmx.de>
To: tim.gardner@canonical.com
Cc: tytso@mit.edu,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Ubuntu Jaunty ext3 --> ext4 upgrade issue
Date: Thu, 19 Feb 2009 10:43:02 +0100	[thread overview]
Message-ID: <200902191043.02880.marvin24@gmx.de> (raw)
In-Reply-To: <499C4F1E.8050901@canonical.com>


Hi Tim,

Am Mittwoch 18 Februar 2009 19:10:38 schrieb Tim Gardner:
> Ted,
>
> I've encountered a situation where the patches that you've proposed for
> stable updates might be causing some issues. This user ivoks appears to
> have an upgrade issue. I assume he's enabled ext4 on an existing ext3
> file system. Hopefully I can get more details. Have you seen anything
> like this?

I had a similar issue with intrepid. To be able to boot from the ext4 fs, I 
installed grub2 from jaunty. The error went away after compiling grub2 from 
source and coping only the ext2.mod to the grub dir. So there must be some 
later updates missing. I guess this is some fallout from 2.6.27/TESTFS or 
similar.

Marvin

> After looking at your for-stable branch, I think I'm missing a couple of
> jbd2 patches. Could they be significant?
>
> rtg
>
> <ivoks> i'm getting 'Invalid or unsupported executable format' from grub
> on all jaunty's generic kernels since (including) 2.6.28-7
> <rtg> ivoks: you must have HW issues. Surely lots of folks would have
> been howling by now.
> <ivoks> could be... but -6 works :/
> <ivoks> even after reinstall of all kernels
> <rtg> have you fsck'd ?
> <ivoks> could try that...
>  it's ext4
> <rtg> ivoks: is it an ext4 upgrade, or was it install time formatted ?
> <ivoks> upgrade
> <rtg> hmm, there were a bunch of ext4 changes that went into -7.18
> <ivoks> right, i've noticed that
> <rtg> ivoks: any change you could build a kernel with all of those
> patches reverted? I expected them via stable updates by now, but perhaps
> Ted has been finding issues with them.
> <ivoks> i could try...
> <rtg> ivoks: they are all labeled 'SAUCE: (revert before 2.6.28.y
> update) ext4:'
> <ivoks> thanks
> <ivoks> only 21 commits :)
> <ivoks> is it possible to build i386 kernel on amd64?
> <rtg> ivoks: you have to chroot the build.
> <ivoks> oh, right!
> <ivoks> rtg: so, reverting all ext4 commits since -6 did the trick
> <rtg> ivoks: can you file a bug with the specifics, and your results
> that I can pass on to Ted ?
> <ivoks> yes, but later... i have to rush now :/
>  take care


      parent reply	other threads:[~2009-02-19  9:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-18 18:10 Ubuntu Jaunty ext3 --> ext4 upgrade issue Tim Gardner
2009-02-18 19:18 ` Peter Zijlstra
2009-02-18 19:24   ` Tim Gardner
2009-02-18 22:25 ` Theodore Tso
2009-02-19 14:24   ` Tim Gardner
2009-02-19 21:10   ` Tim Gardner
2009-02-19  9:43 ` Marvin [this message]

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=200902191043.02880.marvin24@gmx.de \
    --to=marvin24@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim.gardner@canonical.com \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.