From: Theodore Tso <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Adrian Bunk <bunk@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Natalie Protasevich <protasnb@gmail.com>,
linux-ext4@vger.kernel.org
Subject: Re: 2.6.32-rc4: Reported regressions from 2.6.31
Date: Sun, 11 Oct 2009 20:02:12 -0400 [thread overview]
Message-ID: <20091012000212.GA21000@mit.edu> (raw)
In-Reply-To: <alpine.LFD.2.01.0910111608490.3438@localhost.localdomain>
On Sun, Oct 11, 2009 at 04:11:20PM -0700, Linus Torvalds wrote:
>
> On Mon, 12 Oct 2009, Rafael J. Wysocki wrote:
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14370
> > Subject : ext4 corruptions
> > Submitter : Alexey Fisher <bug-track@fisher-privat.net>
> > Date : 2009-10-09 19:20 (3 days old)
> > References : http://marc.info/?l=linux-kernel&m=125511643504864&w=4
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14354
> > Subject : Bad corruption with 2.6.32-rc1 and upwards
> > Submitter : Holger Freyther <zecke@selfish.org>
> > Date : 2009-10-09 15:42 (3 days old)
>
> These two look like duplicates to me. No?
I'm not sure. I'm not able to replicate either failure. According to
Holger, his failure happens after a clean shutdown. Alexey's happens
after a crash/forced power down. So they could possibly be two
separate failures --- although obviously I hope not!
However, Alexey has been posting his failure information in bug
#14354, so we might as well close #14370. What I really need is hints
about how to replicate the failure.
- Ted
prev parent reply other threads:[~2009-10-12 0:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <zJ_pXHNwoHC.A.akB.Aal0KB@chimera>
2009-10-11 23:11 ` 2.6.32-rc4: Reported regressions from 2.6.31 Linus Torvalds
2009-10-12 0:02 ` 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=20091012000212.GA21000@mit.edu \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=protasnb@gmail.com \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).