#633 closed enhancement (wontfix)
Bad Block Instructions - mdadm
Reported by: | Bryan Larsen | Owned by: | Alex Samorukov |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | all | Version: | 6.4 |
Keywords: | Cc: |
Description
The Bad Block Howto should probably contain an mdadm section. mdadm will automatically repair bad blocks, so the section would be pretty short. Here's a first stab:
Linux md/raid will automatically repair a bad block on read by rewriting it. The best way to do this is by performing a scrub on the array:
# echo check > /sys/block/md0/md/sync_action
Follow the progress of the scrub by checking /proc/mdstat:
# cat /proc/mdstat
Change History (5)
comment:1 by , 9 years ago
Milestone: | → unscheduled |
---|---|
Type: | defect → enhancement |
comment:2 by , 9 years ago
Owner: | set to |
---|---|
Status: | new → accepted |
comment:3 by , 9 years ago
The Bad Block Howto is also a good place to mention that the HDD erc timeouts must be set shorter than the controller timeout, to avoid a controller reset (causing loss of all unwritten data and kicking the disk out of the array, possibly making the array unusable) once a bad block is actually found (instead of getting the bad block remapped).
comment:4 by , 7 years ago
Resolution: | → wontfix |
---|---|
Status: | accepted → closed |
I am agree with suggested changes. Bad block howto is now a wiki page with edit rights for the registered users. Please make your changes on https://www.smartmontools.org/wiki/BadBlockHowto directly. Thank you )
comment:5 by , 7 years ago
Milestone: | unscheduled |
---|
I think we should wikify this page and open it to registred users to allow edit. There are a lot of things outdated or not mentioned in this doc, included ZFS, mdraid, SSD specific hints, etc.