All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Alexey Fisher <bug-track@fisher-privat.net>,
	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
Date: Fri, 09 Oct 2009 17:03:35 -0500	[thread overview]
Message-ID: <4ACFB337.8040109@redhat.com> (raw)
In-Reply-To: <alpine.LRH.2.00.0910092351140.12171@twin.jikos.cz>

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

  reply	other threads:[~2009-10-09 22:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-09 19:20 ext4 corruptions Alexey Fisher
2009-10-09 19:20 ` Alexey Fisher
2009-10-09 21:53 ` Jiri Kosina
2009-10-09 21:53   ` Jiri Kosina
2009-10-09 22:03   ` Eric Sandeen [this message]
     [not found]     ` <4ACFB337.8040109-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-10-10  7:29       ` Alexey Fisher
2009-10-10  7:29         ` Alexey Fisher
2009-10-10  0:33 ` Theodore Tso
2009-10-10  0:33   ` Theodore Tso

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=4ACFB337.8040109@redhat.com \
    --to=sandeen@redhat.com \
    --cc=adilger@sun.com \
    --cc=bug-track@fisher-privat.net \
    --cc=jkosina@suse.cz \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --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.