Re: [Evms-devel] EVMS and Drive Linking

[Don M. <dlm...@us...>]

>Do you think DriveLinking can be updated to allow replacing a missing
child
>with another available object? It would basically be a replace without
>copying the data.

Simple enough but the engine is going to barf when it tries to copy sectors
from the missing_child_object to the new available object because reading
from the missing child object will produce lots of EIO return codes.  So,
this seems like a special case that could be handled by a drivelink plug-in
function.  The alternative would be to have a corrupt bit turned on ... in
the missing_child_object ... and the engine tries the copy sectors ... but
ignores any errors.  Then, all you would need to do is remove checks in the
drivelink plug-in replace api routines that check if its dealing with a
replacement object (e.g. lines 2872 and 2873).

-Don