From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 867D2138010 for ; Fri, 26 Oct 2012 03:32:07 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0F93321C0F4; Fri, 26 Oct 2012 03:31:48 +0000 (UTC) Received: from svr-us4.tirtonadi.com (svr-us4.tirtonadi.com [69.65.43.212]) by pigeon.gentoo.org (Postfix) with ESMTP id 7B64D21C016 for ; Fri, 26 Oct 2012 03:30:11 +0000 (UTC) Received: from mail-pa0-f53.google.com ([209.85.220.53]:62129) by svr-us4.tirtonadi.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.77) (envelope-from ) id 1TRabc-002C5w-9D for gentoo-user@lists.gentoo.org; Fri, 26 Oct 2012 10:29:08 +0700 Received: by mail-pa0-f53.google.com with SMTP id bj3so1546713pad.40 for ; Thu, 25 Oct 2012 20:30:10 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.68.209.170 with SMTP id mn10mr66185863pbc.11.1351222210382; Thu, 25 Oct 2012 20:30:10 -0700 (PDT) Received: by 10.68.232.41 with HTTP; Thu, 25 Oct 2012 20:30:10 -0700 (PDT) Received: by 10.68.232.41 with HTTP; Thu, 25 Oct 2012 20:30:10 -0700 (PDT) In-Reply-To: References: <50889166.2000102@fastmail.co.uk> <5088A945.5020405@fastmail.co.uk> Date: Fri, 26 Oct 2012 10:30:10 +0700 Message-ID: Subject: Re: [gentoo-user] Heads-up: Several kernel versions have severe EXT4 data corruption bug From: Pandu Poluan To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=047d7b15a1efdccae604ccedeff4 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - svr-us4.tirtonadi.com X-AntiAbuse: Original Domain - lists.gentoo.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - poluan.info X-Archives-Salt: c5c41276-681a-4762-a38f-024d3e462dfa X-Archives-Hash: 988760c3995354c1a3a82046c5322b5a --047d7b15a1efdccae604ccedeff4 Content-Type: text/plain; charset=UTF-8 On Oct 26, 2012 3:36 AM, "Mark Knecht" wrote: > > On Thu, Oct 25, 2012 at 12:40 PM, Pandu Poluan wrote: > > > > > Nice find, thanks. But the update to that article which gave a link to Theo > > T'so email is quite unnerving. He said that his initial hypothesis had not > > been proven and he himself is back in the dark. > > > > Not much confidence in ext4 for the time being for me. Back to reiserfs? ;-) > > > > Rgds, > > -- > > I'm not an ext4 user (it's too new!) and therefore unaffected by any > of this personally. However I do read lkml and have been following the > thread since it started. This bug, if indeed in the end it's even > determined to be a bug, is apparently pretty hard to hit. The downside > is that if you did hit it the effects can be pretty devastating. > > I'd suggest folks consider going through the thread and not > overreacting to the masking of new kernels or stuff posted on Phoronix > or slashdot. It's good that the info is out there so people can make > informed decisions, but one of the downsides of having all the info is > the potential for people to overreact. Even with a ;-) dumping ext4 > for Reiserfs might be in that camp. :-) > > Cheers, > Mark > LoL... I was just joking about dumping ext4. I still am going to use ext4, but I will ratchet up the backup schedule, and anyone thinking of restarting a Linux server in my office before first performing a full backup, will be severely reprimanded. (I *do* use ReiserFS, though. Especially for portage's tmp) Rgds, -- --047d7b15a1efdccae604ccedeff4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Oct 26, 2012 3:36 AM, "Mark Knecht" <markknecht@gmail.com> wrote:
>
> On Thu, Oct 25, 2012 at 12:40 PM, Pandu Poluan <pandu@poluan.info> wrote:
> <SNIP>
> >
> > Nice find, thanks. But the update to that article which gave a li= nk to Theo
> > T'so email is quite unnerving. He said that his initial hypot= hesis had not
> > been proven and he himself is back in the dark.
> >
> > Not much confidence in ext4 for the time being for me. Back to re= iserfs? ;-)
> >
> > Rgds,
> > --
>
> I'm not an ext4 user (it's too new!) and therefore unaffected = by any
> of this personally. However I do read lkml and have been following the=
> thread since it started. This bug, if indeed in the end it's even<= br> > determined to be a bug, is apparently pretty hard to hit. The downside=
> is that if you did hit it the effects can be pretty devastating.
>
> I'd suggest folks consider going through the thread and not
> overreacting to the masking of new kernels or stuff posted on Phoronix=
> or slashdot. It's good that the info is out there so people can ma= ke
> informed decisions, but one of the downsides of having all the info is=
> the potential for people to overreact. Even with a ;-) dumping ext4 > for Reiserfs might be in that camp. :-)
>
> Cheers,
> Mark
>

LoL... I was just joking about dumping ext4. I still am going to use ext= 4, but I will ratchet up the backup schedule, and anyone thinking of restar= ting a Linux server in my office before first performing a full backup, wil= l be severely reprimanded.

(I *do* use ReiserFS, though. Especially for portage's tmp)

Rgds,
--
=C2=A0

--047d7b15a1efdccae604ccedeff4--