linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Evan King <f11n1@unb.ca>
To: linux-ext4@vger.kernel.org
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: Strange disk failure...could ext4 be the culprit?
Date: Mon, 13 Jul 2009 11:38:52 -0300	[thread overview]
Message-ID: <4A5B46FC.6090808@unb.ca> (raw)
In-Reply-To: <20090713053520.GA5088@skywalker>

Aneesh Kumar K.V wrote:
> On Tue, Jul 07, 2009 at 06:16:23PM +0000, Evan King wrote:
>   
>> Hello all,
>>
>> I'm administering a small computing cluster...
>>
>> _____
>>
>> So my questions are these:
>>
>>  - How likely is it that some arcane bug in ext4 is responsible for the failure?
>>     
>
> Can you check whether your kernel have this patch
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=2ec0ae3acec47f628179ee95fe2c4da01b5e9fc4
>
> -aneesh
>   
Thank you for that bit of sleuthing...what you've unearthed sounds like 
a perfect match for what I experienced.  The system is dual core, and 
the kernel is the latest Ubuntu server (linux-image-2.6.28-13-server).  
I've not been able to find the exact release date of that image (and am 
surprised that release dates are not metadata in apt nor the package's 
web page) but I believe it is too close to the date of this patch to be 
downstream already--and I find no references to this bug in the changelog.

Since there are no launchpad entries referencing this either, I think my 
next step will be to create one pushing for inclusion of this patch in 
the next kernel update, and hopefully for that update to come soon.  My 
cluster has operated smoothly since restoration from backup, and it 
would be nice not to have to reformat (ext partitions were freshly 
created as ext4) or go "aftermarket modding" when a fix is already out.  
At any rate, I have my answer, and it's nice to have a plausible 
explanation--especially one that doesn't point deeper concerns about 
disk load.

Cheers,
 - Evan

      parent reply	other threads:[~2009-07-13 16:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07 18:16 Strange disk failure...could ext4 be the culprit? Evan King
2009-07-07 22:28 ` Andreas Dilger
2009-07-13  5:35 ` Aneesh Kumar K.V
2009-07-13 12:12   ` Theodore Tso
2009-07-13 14:38   ` Evan King [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=4A5B46FC.6090808@unb.ca \
    --to=f11n1@unb.ca \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).