[ 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.
Jiri Kosina wrote:
> [ 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?
>
Not sure if this is the same as
http://bugzilla.kernel.org/show_bug.cgi?id=14354 but it's similarly
lacking in useful info ;)
Please provide the fsck output, any kernel messages, etc ...
-Eric