<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Migratemdisk_grp on BAFM</title><link>https://christian.blog.pakiheim.de/tags/migratemdisk_grp/</link><description>Recent content in Migratemdisk_grp on BAFM</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Thu, 29 Oct 2009 18:09:17 +0000</lastBuildDate><atom:link href="https://christian.blog.pakiheim.de/tags/migratemdisk_grp/index.xml" rel="self" type="application/rss+xml"/><item><title>SVC: Migrate VDisks off a MDisk Group onto another</title><link>https://christian.blog.pakiheim.de/posts/2009-10-29_svc-migrate-vdisks-off-a-mdisk-group-onto-another/</link><pubDate>Thu, 29 Oct 2009 18:09:17 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=2739</guid><description>&lt;p&gt;Out of necessity, another SVC shell script was just born. If you ever need to migrate a whole MDisk group onto another, you quickly discover the limited application of the SVC GUI. Now, you could query the VDisks using your original MDisk Group and then copy and paste the VDisk&amp;rsquo;s name (or the VDisk ID) into a command line and simply reuse that svctask migratevdisk command over and over.&lt;/p&gt;
&lt;p&gt;Luckily IBM blessed the SVC with an SSH interface. So again, we can write a (kinda) simple shell script which may look like this:&lt;/p&gt;</description></item></channel></rss>