From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757553AbZBSVLS (ORCPT ); Thu, 19 Feb 2009 16:11:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754234AbZBSVLA (ORCPT ); Thu, 19 Feb 2009 16:11:00 -0500 Received: from mail.tpi.com ([70.99.223.143]:4734 "EHLO mail.tpi.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754196AbZBSVK7 (ORCPT ); Thu, 19 Feb 2009 16:10:59 -0500 Message-ID: <499DCADB.5060008@canonical.com> Date: Thu, 19 Feb 2009 14:10:51 -0700 From: Tim Gardner Reply-To: tim.gardner@canonical.com User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Theodore Tso , "linux-kernel@vger.kernel.org" Subject: Re: Ubuntu Jaunty ext3 --> ext4 upgrade issue References: <499C4F1E.8050901@canonical.com> <20090218222517.GT3600@mini-me.lan> In-Reply-To: <20090218222517.GT3600@mini-me.lan> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. > >> 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