Mailinglist Archive: opensuse (946 mails)

< Previous Next >
Re: [opensuse] WD Green AV HD: rsync read errors mapping
04.09.2017 05:30, Felix Miata пишет:
Felix Miata composed on 2017-09-03 08:55 (UTC-0400):

Carlos E. R. composed on 2017-09-03 13:46 (UTC+0200):

Felix Miata wrote:

Badblocks on the WD Green AV HD has reached 38.00% completion with (0/0/0
errors) in 47:13:45. :-(

I remember it been very slow. I think it also had a high cpu load, am I

It's varying between 1.6% and 2.4%.

Badblocks on the WD Green AV HD has reached 41.8% completion with (0/0/0
errors) in 51:51:00.

Badblocks 1.42.11 on the WD Green AV HD has reached 51.26% completion with
(4/0/0 errors) in 65:25:00, 4 bad sectors in sequence, but the log's block
numbers have me somewhat perplexed. The output was continuing with 0/0/0 until
well after 41.8% was reached. Now the log shows:


As I didn't specify -b4096 (and should have, given its sloth), those numbers
look like they must be badblocks' own default 1024b block size numbers rather
than logical sector numbers or filesystem block numbers, not really what I
expect it to log on a filesystem formatted with 4k block size (as tune2fs

How is filesystem block size related? badblocks works with device, not
filesystem. From the man page "For this reason, it is strongly
recommended that users not run badblocks directly, but rather use the -c
option of the e2fsck and mke2fs programs".

# fdisk -l
Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 4096 3907029167 1953512536 83 Linux

Is it possible to know whether 1 or 2 4k physical sectors comprise the logged

Something else doesn't make sense. Tune2fs reports lifetime writes of 1223GB,
but the 1863GiB filesystem is 93% full, and certainly has had many files
replaced over its 5 year installed life. I would expect lifetime writes to be
somewhere in the 1.5-3X filesystem size range if not more.

Another thing: I don't see in the badblocks man page what the components of
(#/#/#) are supposed to represent. :-(

Count of (read errors, write errors, corruption errors) where
"corruption" means block read from device differs from block written to

To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >