western digital caviar black. EXT4-fs error

Azat Khuzhin

unread,

Sep 1, 2012, 3:48:24 PM9/1/12

to Linux Kernel Mailing List

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
Aug 28 01:49:03 home-spb kernel: [183245.030956] EXT4-fs error (device
sdc2): ext4_mb_generate_buddy:739: group 4181, 32254 clusters in
bitmap, 32258 in gd
Aug 28 01:49:03 home-spb kernel: [183245.030980] EXT4-fs error (device
sdc2): ext4_mb_generate_buddy:739: group 2600, 32254 clusters in
bitmap, 32258 in gd
Aug 28 01:49:03 home-spb kernel: [183245.061866] EXT4-fs error (device
sdc2): ext4_mb_generate_buddy:739: group 9305, 32254 clusters in
bitmap, 32258 in gd
Aug 28 01:49:03 home-spb kernel: [183245.061892] EXT4-fs error (device
sdc2): ext4_mb_generate_buddy:739: group 8230, 32254 clusters in
bitmap, 32258 in gd
Aug 28 01:49:40 home-spb kernel: [183281.733813] EXT4-fs error (device
sdc2): ext4_mb_generate_buddy:739: group 2477, 32254 clusters in
bitmap, 32258 in gd
Aug 28 01:49:40 home-spb kernel: [183281.743131] JBD2: Spotted dirty
metadata buffer (dev = sdc2, blocknr = 0). There's a risk of
filesystem corruption in case of system crash.
Aug 28 01:50:13 home-spb kernel: [183314.898637] EXT4-fs error (device
sdc2): ext4_mb_generate_buddy:739: group 3139, 32254 clusters in
bitmap, 32258 in gd
Aug 28 01:50:58 home-spb kernel: [183359.783544] EXT4-fs error (device
sdc2): ext4_mb_generate_buddy:739: group 4061, 32254 clusters in
bitmap, 32258 in gd
Aug 28 01:50:58 home-spb kernel: [183359.783577] EXT4-fs error (device
sdc2): ext4_mb_generate_buddy:739: group 8166, 32254 clusters in
bitmap, 32258 in gd
Aug 28 01:51:08 home-spb kernel: [183369.757927] EXT4-fs error (device
sdc2): ext4_mb_generate_buddy:739: group 8171, 32254 clusters in
bitmap, 32258 in gd
Aug 28 16:06:54 home-spb kernel: [234584.906721] EXT4-fs (sdc2): error count: 26
Aug 28 16:06:54 home-spb kernel: [234584.906725] EXT4-fs (sdc2):
initial error at 1346069075: ext4_mb_generate_buddy:739
Aug 28 16:06:54 home-spb kernel: [234584.906727] EXT4-fs (sdc2): last
error at 1346104268: ext4_mb_generate_buddy:739

One time, machine rebooted (not manually), when I turn it on, it runs
fsck on /dev/sdc2 and fix some errors and some files are missing on
/dev/sdc2

I'v check /dev/sdc2 for badblocks, it doesn't have it ( using e2fsck
-c /dev/sdc2 )
Here is the output of fsck http://pastebin.com/D5LmLVBY

What else I can do to understand what's wrong here?

BTW for /dev/sdc1 no message like that, in kern.log

Linux version: 3.3.0
Distributive: Debian wheezy

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

Azat Khuzhin

unread,

Sep 1, 2012, 3:54:06 PM9/1/12

to Linux Kernel Mailing List

I'v also post question here

http://serverfault.com/questions/423565/western-digital-caviar-black-ext4-fs-error

Azat Khuzhin

unread,

Sep 3, 2012, 4:07:44 PM9/3/12

to Linux Kernel Mailing List

Anybody?

Theodore Ts'o

unread,

Sep 3, 2012, 11:16:45 PM9/3/12

to Azat Khuzhin, Linux Kernel Mailing List

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

Azat Khuzhin

unread,

Sep 4, 2012, 4:37:59 PM9/4/12

to Linux Kernel Mailing List

Ted, many thanks!
I'll try to compile new kernel (maybe 3.4.x)

Azat Khuzhin

unread,

Sep 4, 2012, 5:39:05 PM9/4/12

to Linux Kernel Mailing List

Ted, Thanks!
It fix my problem.