public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Heads-up: Several kernel versions have severe EXT4 data corruption bug
Date: Fri, 26 Oct 2012 10:30:10 +0700	[thread overview]
Message-ID: <CAA2qdGW_3-onWsdWstCtMm6ZgQBW7F=nYwQ1orsogVcDKADH-w@mail.gmail.com> (raw)
In-Reply-To: <CAK2H+ed+-5UYJHMqVh6A=r03=AnW_MuUjyA9Z640r7YMe2Bj1w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1566 bytes --]

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 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,
--

[-- Attachment #2: Type: text/html, Size: 2013 bytes --]

  reply	other threads:[~2012-10-26  3:32 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24 13:54 [gentoo-user] Heads-up: Several kernel versions have severe EXT4 data corruption bug Nikos Chantziaras
2012-10-24 14:42 ` Dale
2012-10-24 15:22   ` covici
2012-10-24 14:43 ` Paul Hartman
2012-10-24 14:48 ` Markos Chandras
2012-10-24 18:10 ` Bruce Hill
2012-10-24 22:36   ` john
2012-10-24 23:55     ` mindrunner
2012-10-25  0:55 ` Canek Peláez Valdés
2012-10-25  1:09   ` Kerin Millar
2012-10-25  1:32     ` Canek Peláez Valdés
2012-10-25  1:38     ` Canek Peláez Valdés
2012-10-25  2:51       ` Kerin Millar
2012-10-25  3:03         ` Michael Mol
2012-10-25 19:40           ` Pandu Poluan
2012-10-25 20:10             ` Dale
2012-10-26  0:34               ` Neil Bothwick
2012-10-26  8:29                 ` Dale
2012-10-27 19:16                 ` Volker Armin Hemmann
2012-10-28 17:12                   ` Mark Knecht
2012-10-26  3:26               ` Pandu Poluan
2012-10-26  8:16                 ` Dale
2012-10-25 20:33             ` Mark Knecht
2012-10-26  3:30               ` Pandu Poluan [this message]
2012-10-25 23:10             ` Michael Mol
2012-10-26  3:37               ` Pandu Poluan
2012-10-25  3:04         ` Canek Peláez Valdés
2012-10-25  4:43           ` [gentoo-user] " Nikos Chantziaras
2012-10-25 14:26         ` Grant Edwards
2012-10-25 16:53           ` Remy Blank
2012-10-25 21:04           ` Kerin Millar
2012-10-27 18:19             ` Volker Armin Hemmann
2012-10-27 18:28               ` Canek Peláez Valdés
2012-10-29 10:29 ` [gentoo-user] " Helmut Jarausch
2012-11-02 13:45   ` Kerin Millar
2012-11-02 14:55     ` Dale
2012-11-02 15:05       ` Michael Mol
2012-11-02 15:08       ` Paul Hartman
2012-11-02 16:08       ` Kerin Millar
2012-11-02 20:19         ` Dale

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='CAA2qdGW_3-onWsdWstCtMm6ZgQBW7F=nYwQ1orsogVcDKADH-w@mail.gmail.com' \
    --to=pandu@poluan.info \
    --cc=gentoo-user@lists.gentoo.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