Tracker: Bugs
When marking badblocks in the destination is enabled, safecopy reads the
next block number from the include file to see where it is allowed to
write.
This leads to a situation where safecopy treats all blocks between the last
attempted read block and the next include block as include blocks, too,
even while they are not.
Reproduction:
an include file with two sets of blocks.
badblock marking enabled.
the last block of the first set of include blocks fails to read, getting
marked as bad.
Expected result:
bad block gets marked, then safecopy skips to the first block in the second
group of include blocks and continues there.
Actual result:
bad block gets marked, then safecopy copies ALL the blocks towards and
including the second group of include blocks!
This bug will be permanently fixed in safecopy 1.6
a hotfix patch will be provided beforehand asap.
Eric Noack
Safecopy Core
None
Public
Comment ( 1 )
|
Date: 2009-09-09 18:17 Fixed the bug with release 1.6 |
Log in to comment.
Attached File ( 1 )
| Filename | Description | Download |
|---|---|---|
| safecopy-1.5-iblocks-bugfix.patch | patch to fix bad block include file handling | Download |
Changes ( 3 )
| Field | Old Value | Date | By |
|---|---|---|---|
| resolution_id | Accepted | 2009-09-09 18:17 | corvuscorax |
| File Added | 342350: safecopy-1.5-iblocks-bugfix.patch | 2009-09-09 16:31 | corvuscorax |
| resolution_id | None | 2009-09-08 13:12 | corvuscorax |
