From: Tim Gardner <tim.gardner@canonical.com>
To: Theodore Tso <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 14:10:51 -0700 [thread overview]
Message-ID: <499DCADB.5060008@canonical.com> (raw)
In-Reply-To: <20090218222517.GT3600@mini-me.lan>
Theodore Tso wrote:
> On Wed, Feb 18, 2009 at 11:10:38AM -0700, Tim Gardner wrote:
>> 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?
>
> No, this is the first I've heard of it.
>
>> <ivoks> i'm getting 'Invalid or unsupported executable format' from grub
>> on all jaunty's generic kernels since (including) 2.6.28-7
>
> So grub is complaining that it can't boot from a partition after
> upgrading to the new kernel with the for-stable patches? Um, that's
> interesting. So the obvious thing to check is to do an md5 checksum
> of the kernel in /boot to make sure it didn't get corrupted somehow.
> The other thing to check would be to ask the user to run e2fsck to
> rule out filesystem corruption.
>
> OTOH, if this was just a simple install and upgrade, presumably the
> new kernel would have been installed while the previous kernel was
> booted.
>
> I do my testing by using a ext3 /boot partition (since my
> crash-and-burn netbook is running Ubuntu Jaunty). So I wouldn't have
> noticed anything, but this seems very odd.
>
> More information would be useful; is there a Launchpad bug open on this yet?
>
> Or we can work this out on LKML or the linux-ext4 mailing list if the
> reporter is willing to be cc'ed on the thread....
>
> - Ted
>
False alarm. It turned out to be a grub issue, though I'm not sure how
the user got to that point without having also upgraded grub.
rtg
--
Tim Gardner tim.gardner@canonical.com
next prev parent reply other threads:[~2009-02-19 21:11 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 [this message]
2009-02-19 9:43 ` Marvin
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=499DCADB.5060008@canonical.com \
--to=tim.gardner@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--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.