RE: [Evms-devel] EVMS and Drive Linking

[Stian B. B. <sti...@it...>]

Dun Mulvey wrote:
>The storage for the drivelink is replaced using an available storage
>object.  You can look under the available objects tab for candidates.
Its
>possible to have regions or partitions or even another drivelink
storage
>object that's suitable but it seems in your case that you must have had
a
>disk object in the avail object list that was sufficiently large for
the
>replace and others just were not suitable.

The replacement disk is exactly the same make and size as the one that
was removed (or simulated defect), thus not large enough to accommodate
the rest of the Drive Link.

[snip]
>You removed the middle disk ... this is a hole in the middle of your
>drivelink object.  It really makes no sense to rebuild with your 2
existing
>objects ... UNLESS ... you first shrink the drivelink.  If the file
system
>allows you to shrink down to the very first object in the link then
your
>home free!  Just shrink the drivelink down to the 1st disk and follow
the
>shrink with an expand that would pick up the disk you just freed by
>shrinking ... moving the 3rd disk down to the 2nd disk spot.

I get no option to shrink. It just says that the Drive Link is "Read
Only" and I am not even able to run a fschk or mount to the volume. I
need to be able to run an fschk before I can resize. I am running
ReiserFS so shrinking should be possible (when it's rw and I have run an
fschk).=20

>>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.

This is OK. All I want is to replace my faulty disk with a new, then fix
the file system as best I can, and be able to again use my Drive Link.
Data loss is accepted but I want my volume back in a Read+Write kinda
way! :)

Best regards
Stian B. Barmen