OLE DB Destination - Redirecting Rows

I'm getting some strange error handling behaviour when I tried to redirect rows when an error is encountered at the OLE DB Destination. I enabled the fastload option and set the maximum insert commit size to 10,000. My package is trying to insert 1,000,000 rows. When the row containing bad data is encountered, the entire batch is redirected to a separate table with no table constraints. So I have approx 990,000 rows of good data inserted, and approx 10,000 rows in an error table. However, only 2 of the 10,000 rows are actually bad data.

I changed the filter in the data source to reload 5 rows from the 10,000 rows of bad data. The 5 rows include the 2 rows of bad data. The fastload option and max insert commit size at the OLE DB Destination are not changed. When the package completed, 3 rows were inserted to the destination and the 2 bad rows are redirected again. Even though this is the outcome I wanted (only the real bad data is redirected), shouldn't all 5 rows be redirected since they should all be treated as a single batch?

My second question is, is there a way to get the best of both worlds - be able to load lots of data as fast as possible and only redirect the rows that are actually bad?

Thanks.