Re: Using the new bad-block-log in md for Linux 3.1

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

 



On Wed, 27 Jul 2011, keld@xxxxxxxxxx wrote:

So because of the sometimes low number of intrinsic disk reserve blocks, there would be a point in having this facility replicated in the md layer.

I don't agree at all. I remember back in the old MFM/RLL drive days and I don't want to go back there. If a drive has filled up its bad block reloaction area with relocated blocks, then it's time to RMA that drive and get a new one. It's obviously defective.

The added complexity the bad block scheme you propose would add to the code base is worrysome, I'd rather just go with what Neil has suggested so far. The hot-replace functionality is a really really needed feature and I imagine it can be done much more cleanly without having to duplicate the bad block reallocation functionality the drives already have.

--
Mikael Abrahamsson    email: swmike@xxxxxxxxx
--
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