Re: [Evms-devel] EVMS and Drive Linking

[Kevin C. <kev...@us...>]

On Monday 02 June 2003 08:53, Don Mulvey wrote:
> >Right clicking the "ld-missing_child_1" does not present a "Replace..."
> >option.
>
> I think you realize at this point that ld-missing_child_1 is not an area on
> any disk in your system.  It is simply a place holder that provides a DM
> error mapping ...  so that the drivelink can be constructed and recoverd by
> restoring the missing object or by shrinking the drivelink.  It makes no
> sense for you to replace the missing object ... it means that your going to
> find an available object and then copy the contents of ld-missing_child_1
> to the object ... only the i/o is going to fail during the copy because
> there is not storage backing the missing child.

But...it would still be nice to have some option (be it replace or some 
DriveLinking private-function) to stick in a clean child where the missing 
child used to be. Obviously this operation would have to skip the "copy" 
portion of the replace.

For example, in the LVM plugin, if a PV is missing, you can do a "Move-PE" to 
change the mapping of the affected LE to some other available PE in the 
container. The "Move-PE" command simply skips the copy if the source PE is 
missing. This allows the user to get their volume back to a functional state, 
even if the data within the volume might be trashed.

-- 
Kevin Corry
kev...@us...
http://evms.sourceforge.net/