linux-kernel - Re: western digital caviar black. EXT4-fs error

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120904031544.GI5066@thunk.org>
Date:	Mon, 3 Sep 2012 23:15:44 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Azat Khuzhin <dohardgopro@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: western digital caviar black. EXT4-fs error

On Sat, Sep 01, 2012 at 11:48:17PM +0400, Azat Khuzhin wrote:
> Recently I update my HDD on desktop machine, and bought WD Caviar Black.
> But after I format & copy information to it (using dd), and fix
> partitions size: I have next errors in kern.log:
> 
> Aug 28 01:49:03 home-spb kernel: [183245.030897] EXT4-fs error (device
> sdc2): ext4_mb_generate_buddy:739: group 3675, 32254 clusters in
> bitmap, 32258 in gd

Sorry for the delay; you sent this to linux-kernel (and not the
linux-ext4 list).  It also took me a while to dig up the relevant fix
from my archives; normally, once a bug has been fixed (as this one
was, on June 7, 2012) I don't worry about it any more.

The upstream fix is commit b0dd6b70f0fda17ae9762fbb72d98e40a4f66556.

Note that you are using the 3.3.0 kernel.  This is a not long-term
supported kernel, so fixes from upstream are no longer being
backported to it.  The official Debian kernel (which tracks the 3.2.x
stable kernel series) has the backported bug fix.  So does the 3.4
long-term stable kernel series, as does the 3.5 kernel or any later
kernel.

If you don't know how to backport a kernel patch, or even if you do, I
would strongly suggest that you either go back to the Debian standard
kernel for Wheezy, or track the 3.2.x or 3.4.x long-term stable
kernel.  (The fix is in v3.2.20 or later, and v3.4.3 or later ---
where those trees are up to v3.2.28, and v3.4.10, respectively.)
Otherwise, you may very well run into some other kernel bug which has
already been fixed upstream, and you'll just waste your time as well
as various other kernel developers.

Regards,

						- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/