atrocity

So one of my scans with Scanner found 32 sectors that are bad and can't be remapped, so DrivePool started evacuating the drive. Scanner continued on and is finding no more after it... I'm assuming one of my kids or dog or something bumped into my one desk while data was being written. I don't have enough space in the pool to evacuate all the data, so it's kinda given up. Is there a way to tell it to keep the drive in the pool and write data to it (since it's 100% full now...don't exactly want to buy a new 8 TiB drive) just like always, just knowing that sector is bad? Or will it pull it back into a "valid" state after the scan 100% finishes the drive? Also, if it DOES do that, will it know the copies on the other drives are the "real" copies and to not use these "corrupted" copies for replication later?