On Monday 07 of December 2015, Arkadiusz Miskiewicz wrote: > Anyway I would expect my problem to be related to badblock lists which > numbers are close to dmesg error message: [ 848.988518] Buffer I/O error > on dev md7, logical block 3907148544, async page read > > > >> http://sprunge.us/XSWI > > But how to repair these if write() also fails and > http://www.spinics.net/lists/raid/msg49325.html suggests that write should > "fix" these (by using replacement blocks I guess) ? Tried to get rid of badblock lists (well, corruption in that area is better than no access at all): mdadm --assemble /dev/md7 --force --update=no-bbl mdadm: Cannot remove active bbl from /dev/sdae1 mdadm: Cannot remove active bbl from /dev/sdag1 mdadm: Cannot remove active bbl from /dev/sdai1 mdadm: Cannot remove active bbl from /dev/sdn1 mdadm: Cannot remove active bbl from /dev/sdg mdadm: Cannot remove active bbl from /dev/sdad1 mdadm: /dev/md7 has been started with 10 drives. Is there a way to archieve that anyway? -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) -- 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
