Fwd: strange problem with raid6 read errors on active non-degraded array

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

 





Hi Ethan,

The thing here is that some of the bad blocks ( if not all ) that are giving read errors are not on the bad blocks list. Specifically, the ones that show up when doing a fsck are not on any drive. For these sectors fsck tries to re-write then and md still throws an error but they are not added to the list and the disk doesn't drop from the array.

I replaced sdm with a new disk. this was one that had a bunch or bad blocks reported by md, and after finishing the rebuild ( with no errors at all ) the --examine-badblocks still gives me the exact same list of errors. I would expect that replacing the disk by a new one would clear the errors.

as I know the disks are good, is there any way of reseting the bad blocks list without destroying the filesystem?

cheers
Pedro



________________________________________________________________________________
Mensagem enviada através do email grátis AEIOU
http://www.aeiou.pt
--
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