19

The record will be wiped out in
a different way.

I tried disturbing the timeing with break-
points and the same wipe happened. This
suggests that the bug may be insensitive
to timeing but sensitive to a lot of history
of writes. Putting a read after every write,
as I did to find the write that was
getting us, didn't effect it.

I tried completely the pattern of
writes, hitting every sixth record instead
of every fifth. No change. The data from
record 207100 is still being put in record
207000 when writing on record 216100, as
stated in the middle of page 11.

I took the disk off-line and zeroed it,
then ran the test again. Same trouble. But
record 207100 hadn't yet been written!
The data on record 207000 is being marked
rather than over-written by another record.