atom feed30 messages in org.freebsd.freebsd-currentRe: A tool for remapping bad sectors ...
FromSent OnAttachments
Eugeny N DzhurinskyMar 8, 2010 2:26 am 
Alexander MotinMar 8, 2010 2:31 am 
Eugene DzhurinskyMar 8, 2010 2:52 am 
Eugene DzhurinskyMar 8, 2010 2:54 am 
Eugene DzhurinskyMar 8, 2010 3:08 am 
Miroslav LachmanMar 8, 2010 3:21 am 
Wes MorganMar 8, 2010 3:46 am 
Eugene DzhurinskyMar 8, 2010 3:50 am 
Miroslav LachmanMar 8, 2010 5:28 am 
Alex KedaMar 8, 2010 12:14 pm 
Ulrich SpörleinMar 11, 2010 5:47 am 
Dag-Erling SmørgravMar 11, 2010 7:20 am 
Svein Skogen (Listmail Account)Mar 11, 2010 7:23 am 
Miroslav LachmanMar 13, 2010 12:44 pm 
Dag-Erling SmørgravMar 13, 2010 1:24 pm 
Miroslav LachmanMar 14, 2010 1:54 am 
Gary JennejohnMar 14, 2010 4:38 am 
Miroslav LachmanMar 14, 2010 9:18 am 
Gary JennejohnMar 14, 2010 10:47 am 
Dag-Erling SmørgravMar 17, 2010 3:58 am 
Miroslav LachmanMar 17, 2010 4:35 am 
Miroslav LachmanMar 17, 2010 4:41 am 
Dag-Erling SmørgravMar 17, 2010 4:59 am 
Gary JennejohnMar 17, 2010 5:05 am 
Miroslav LachmanMar 18, 2010 3:29 am 
Miroslav LachmanMar 18, 2010 3:32 am 
Dag-Erling SmørgravMar 18, 2010 4:10 am 
Pieter de GoejeMar 18, 2010 4:33 am 
Miroslav LachmanMar 18, 2010 4:45 am 
Dag-Erling SmørgravMar 18, 2010 5:17 am 
Subject:Re: A tool for remapping bad sectors in CURRENT?
From:Dag-Erling Smørgrav (de@des.no)
Date:Mar 18, 2010 4:10:44 am
List:org.freebsd.freebsd-current

Miroslav Lachman <000.@quip.cz> writes:

As you can see, there are really two different numbers LBA=79725056 in messages and LBA = 0x04c0826f = 79725167 in SMART log.

I don't know how comfortable you are reading kernel code, but I would suggest looking through the atadisk driver to see why the numbers are different.

And if you're comfortable *writing* kernel code, I would suggest implementing WORF in geom_mirror :)

DES