RE: [Evms-devel] EVMS and Drive Linking

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

>Thanks! I did this, and started EVMSN, and the drive link now suddenly
>contained the replacement hdc automatically (including the faulty

Not possible ... unless ... hdc had old drivelink metadata on it.  Did it?
What was the last thing you used this disk for?   When you run evmsn or
evmsgui or whatever ... and you delete a storage object ... the plug-in
managing the storage object will delete its metadata so that you won't
discover the storage object the next time you run evms and you wont
discover the storage object unexpectedly if you move the disk to a
different system.  If you simply pull the disk from a system it will still
have metadata on it ... which is generally not a good thing.  There is
simply no way that your drivelink suddenly contained a replacement disk ...
unless ... the disk had old drivelink metadata on it or else it was
deliberately added.  Perhaps your saying that you did a replace on the
missing child object??

>placeholder, and reporting total size 2 gb too large!). Sadly I did not
just

Guessing that hdc was a 2gb drive ...

>escape and try again, but rather saved. The result was disaster, all the

What changes did you save.  Just starting evms and saving will generally
just activate DM mappings.  If you haven't made any configuration changes
then you should not have saved any configuration changes.

>disks were available again (empty like) and the Feature object
disappeared.

>Oh well. I try again. Have just set up the drive link again, filled it
with
>data, and I am currently killing off the hdb drive (the first in the drive
>link). This time I chose ext3 file system. Fingers crossed!

Looking forward to hearing about this attempt.

-Don