On 04/05/17 11:04, Ravi (Tom) Hale wrote: > Since btrfs doesn't support badblocks, this btrfs mailing list post[1] > suggested to use mdadm RAID0 3.1+. Having read the email you linked to, I don't think mdadm will be any help at all ... > > Is there a way of having blocks from a spare device automatically > replacing bad blocks when they are next written to (like SMART does for > HDDs)? What quite do you mean? > > Or would mdadm be able to add a "badblocks layer" to btrfs in some other > way? No. With modern hard drives, no filesystem should pay any attention to badblocks - it's all handled in the drive firmware. Badblocks is an unfortunate legacy from the past when drives really were CHS, and the layer above needed some way of knowing which blocks were bad and should be avoided. mdadm has had a lot of grief with its handling of badblocks, and getting drives confused, and it's all totally unnecessary anyway. Let the drive worry about what blocks are bad. One major point behind LBA is it hides the actual disk layout from the computer, and allows the drive to relocate blocks that aren't working properly. Let it do its job. If you want to use raid, don't bother with 0. Use mdadm and raid 5 or 6 to combine your drives, and create a btrfs filesystem on top. (Don't bother with raid1 - that part of btrfs apparently works well, so use the filesystem variant, not an external one.) > > My use case is mining storj - I don't mind some data loss. Using a badblock list will have no impact on this whatsoever. > > [1] https://www.spinics.net/lists/linux-btrfs/msg40909.html > Cheers, Wol -- 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
