> Could we have a config setting for removing the bad blocks list on > assembly? > > I'm aware that one could put: > > CREATE bbl=no > > in mdadm.conf and then newly created arrays won't have a bad blocks > list. But in many cases, system arrays are created before an > mdadm.conf exists, so they get a bbl. > > So, to remove a bbl I know that you have to stop the array and > assemble it like: > > # mdadm /dev/mdX --assemble --update=no-bbl > > Again, for arrays with the actual system on it this is rather > inconvenient. Even having to have some downtime of the service to do > this is not great. > > So how about a config option telling mdadm to remove empty bbl the > next time arrays are assembled? If there is a bbl with entries in it > then it could warn and not remove it (so no force). …or just remove the whole bbl, since it has virtually no function and didn't even have it when it was introduced 10 years ago. Even back then, drives had automatic reallocation of bad sectors and even if the docs say the bbl is built on write errors alone, this seems to not be the case. If a drive is bad, it should get thrown out, not patched up in software in the belief that this will make things better. That the bbl is replicated to new members and thus never removed, is part of this. I posted a thread about this earlier. Vennlig hilsen roy -- Roy Sigurd Karlsbakk (+47) 98013356 http://blogg.karlsbakk.net/ GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt -- Hið góða skaltu í stein höggva, hið illa í snjó rita.
