[<prev] [next>] [day] [month] [year] [list]
Message-ID: <292801cabbca$829e365e$2303d30a@fsl.freescale.net>
Date: Fri, 5 Mar 2010 00:11:01 +0530
From: "Kalra Ashish-B00888" <B00888@...escale.com>
To: "Mark Lord" <kernel@...savvy.com>, "foo saa" <foosaa@...il.com>
Cc: "Greg Freemyer" <greg.freemyer@...il.com>,
"Andrew Morton" <akpm@...ux-foundation.org>,
<linux-kernel@...r.kernel.org>, <linux-ide@...r.kernel.org>,
"Jens Axboe" <jens.axboe@...cle.com>, <linux-mm@...ck.org>
Subject: RE: Linux kernel - Libata bad block error handling to user mode program
Sent from my HTC
-----Original Message-----
From: Mark Lord <kernel@...savvy.com>
Sent: 04 March 2010 11:20 PM
To: foo saa <foosaa@...il.com>
Cc: Greg Freemyer <greg.freemyer@...il.com>; Andrew Morton <akpm@...ux-foundation.org>; linux-kernel@...r.kernel.org <linux-kernel@...r.kernel.org>; linux-ide@...r.kernel.org <linux-ide@...r.kernel.org>; Jens Axboe <jens.axboe@...cle.com>; linux-mm@...ck.org <linux-mm@...ck.org>
Subject: Re: Linux kernel - Libata bad block error handling to user mode program
On 03/04/10 10:33, foo saa wrote:
..
> hdparm is good, but I don't want to use the internal ATA SECURE ERASE
> because I can never get the amount of bad sectors the drive had.
..
Oh.. but isn't that information in the S.M.A.R.T. data ??
You'll not find the bad sectors by writing -- a true WRITE nearly never
reports a media error. Instead, the drive simply remaps to a good sector
on the fly and returns success.
Generally, only READs report media errors.
Cheers
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
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/
Powered by blists - more mailing lists