From: Theodore Tso <tytso@mit.edu>
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>
Subject: Re: ext4 corruptions
Date: Fri, 9 Oct 2009 20:33:39 -0400 [thread overview]
Message-ID: <20091010003339.GB18440@mit.edu> (raw)
In-Reply-To: <1255116014.3014.8.camel@mini>
On Fri, Oct 09, 2009 at 09:20:13PM +0200, 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.
>
> 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?
Can you reproduce this reliably? What sort of things did fsck report?
Was it after a suspend/resume that failed?
I'm using a Ubuntu 9.04 with a 2.6.32-rc1+ mainline kernel, and it
works fine for me. So we really need many more details what sort of
filesystem corruption (not just "bad things"), and more details about
what you did while testing a newer kernel, and what sort of things
fsck complained about.
- Ted
prev parent reply other threads:[~2009-10-10 0:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 19:20 Alexey Fisher
2009-10-09 21:53 ` Jiri Kosina
2009-10-09 22:03 ` Eric Sandeen
2009-10-10 7:29 ` Alexey Fisher
2009-10-10 0:33 ` Theodore Tso [this message]
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=20091010003339.GB18440@mit.edu \
--to=tytso@mit.edu \
--cc=bug-track@fisher-privat.net \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®