Date: Fri, 9 Oct 2009 23:53:24 +0200 (CEST)
From: Jiri Kosina <jkosina@suse.cz>
To: Alexey Fisher <bug-track@fisher-privat.net>
Cc: Kernel Testers List <kernel-testers@vger.kernel.org>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       linux-ext4@vger.kernel.org, "Theodore Ts'o" <tytso@mit.edu>,
       Andreas Dilger <adilger@sun.com>
Subject: Re: ext4 corruptions
In-Reply-To: <1255116014.3014.8.camel@mini>
Message-ID: <alpine.LRH.2.00.0910092351140.12171@twin.jikos.cz>
References: <1255116014.3014.8.camel@mini>
User-Agent: Alpine 2.00 (LRH 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1033
Lines: 29


[ adding some CCs so that this doesn't get lost in the lkml wilderness ]

On Fri, 9 Oct 2009, Alexey Fisher wrote:

> I have really bad ext4 corruptions, i needed to reinstall 3 of my test
> systems.
> The symptoms:
> is use karmic beta for this with ubuntu supplied kernel 2.6.31 ... after
> testing 2.6.32-rc[1-3] and booting again to 2.6.31 fsck will find some
> bad things and will try to fix it. After this action is the system
> unusable.

Does this happen also when you switch from vanilla 2.6.32-rcX to vanilla 
2.6.31, or only from vanilla 2.6.32-rcX to "Ubuntu 2.6.31"?

> Do any one had same problem? The is no sans to bisect it, after some
> jumps between 2.6.31 and 2.6.32 the system will be broken.  Is it kernel
> or fsck problem?

-- 
Jiri Kosina
SUSE Labs, Novell Inc.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/