solve link missing child object problem

Arjen de Rijke <[email protected]>
Newsgroups gmane.linux.evms.devel
Message-ID <[email protected]>
Hi,

We are having a problem with one of our evms volumes. The volume is a 
DriveLink object with two connected harddisc segments on two different 
harddiscs. After a reboot, the volume was not available and the evmsgui 
indicated that the volume was missing a child. The correct segment was 
replaced bij a "link_missing_child" DriveLink object. The correct disk 
segment is available in the "available object" tab.

The context menu of the "link_missing_child" object has an option 
"Replace Missing Child". If i select this, i get a screen with the 
available objects, containing the correct disc segment. I hope / guess 
that this would restore the original configuration and solve our problem.

But because the volume contains valueable data, i want to be really sure 
this doesn't go wrong. Does anybody have experience with this kind of 
problem? And can anybody confirm that replacing the missing child object 
  makes the volume available again without corrupting the filesystem? Or 
is there a better way to solve this problem? And is there a way to 
backup the meta_data when the "backup" option in the "action" menu of 
evmsgui gives an error?

The volume is an 12 TB XFS filesystem, evms is version 2.5.3 on Suse 
Linux 10.0 on a x86_64 system.

Thanks in advance,

Arjen de Rijke


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Evms-devel mailing list
[email protected]
To subscribe/unsubscribe, please visit:
https://lists.sourceforge.net/lists/listinfo/evms-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.