Re: [Evms-devel] EVMS and Drive Linking

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

On Friday 30 May 2003 08:35, Stian B. Barmen wrote:
> Hello Kevin, I am running tests now. Already come to a puzzle.
>
> Have a drive link called "ld" with 3x2gb disks, removed the middle (nr.
> 2 disk) for test. Now the volume reports "ld-missing_child_1", and if I
> right click the "ld" feature object I get the Replace... option. Now, if
> I choose the Replace.. then I can replace the DriveLink with a drive.
> This seems to copy all the data from the Feature Object directly to the
> new disk.

Yes. When you click on the DriveLink object and choose "replace", you are 
actually replacing the DriveLink object with something else, from the point 
of view of the volume on top of the DriveLink. Thus, it tries to read all the 
data from the DriveLink and move it to some other location (the new disk in 
your case). The result being that the Volume then maps just to the disk, and 
no longer to the DriveLink.

> What I want to do is to replace the disk in the feature object, or just
> rebuild with the 2 existing objects and just remove the "missing_child".
> Right clicking the "ld-missing_child_1" does not present a "Replace..."
> option.
>
> How can I do this?

Yes, we need to provide the option for "replace" on the "ld-missing-child-1" 
object. After the same test on my system, I noticed it doesn't give this 
option. It *does* give the "replace" option when you click on the remaining 
real disks in the DriveLink. I will talk with Don next week about how we can 
add the option to replace missing children from a DriveLink.

> When this is done I guess that a fsch.reiserfs --rebuild-tree is in
> place, but I will wait further instructions before I go forward.

Have you tried testing the volume as-is (with the missing child)? How does the 
filesystem respond?

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