Re: Raid and badblocks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 30/05/2009 11:13, hank peng wrote:
2009/5/26 Andrew Burgess <aab@xxxxxxxxxxx>:
On Tue, 2009-05-26 at 13:59 +0100, Jeremy Sanders wrote:

Strangely, the Reallocated_Sector_Ct is still zero on the drive even though
Current_Pending_Sector is now zero. This is a Samsung HD103UJ by the way.
That can be ok. It probably tried writing and then rereading and when
that worked it decided the sector didn't really have a 'hard' error
(like a physical defect on the platter) and thus didn't need to be
reallocated to a spare sector. You could generate an unreadable sector
during a write by the power failing or with excessive vibration.

I have a question, in this situation, if I do as Jeremy did, write
zero to bad block to make drive think it is not bad any more, then
what about old data? Isn't it lost?

In Jeremy's case, the bad block was past the end of the data in the array, so no, data wasn't lost. If the bad block had been within the array data, the repair operation he ran earlier would have found it, reconstructed the correct data from the other drives, and rewritten it, again avoiding any data loss.

Cheers,

John.

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux