linux-ext4 - Re: Strange disk failure...could ext4 be the culprit?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 13 Jul 2009 11:38:52 -0300
From:	Evan King <f11n1@....ca>
To:	linux-ext4@...r.kernel.org
CC:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
Subject: Re: Strange disk failure...could ext4 be the culprit?

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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html