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

Message-ID: <CAAW1UO-q5uUe4zG5BnB0z9dyKCqRRWH4sriyu7Fj6XinE7GKzA@mail.gmail.com>
Date:	Sat, 1 Sep 2012 23:48:17 +0400
From:	Azat Khuzhin <dohardgopro@...il.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: western digital caviar black. EXT4-fs error

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