{"id":513,"date":"2009-12-02T16:40:55","date_gmt":"2009-12-02T15:40:55","guid":{"rendered":"http:\/\/glandium.org\/blog\/?p=513"},"modified":"2010-01-27T08:52:22","modified_gmt":"2010-01-27T07:52:22","slug":"removing-a-vmfs-extent","status":"publish","type":"post","link":"https:\/\/glandium.org\/blog\/?p=513","title":{"rendered":"Removing a VMFS extent"},"content":{"rendered":"<p>Until vSphere 4, the only way to add space to an existing VMFS was to add an extent. This means creating a new partition, most of the time on a new LUN, and extend the VMFS there (vSphere 4 is now able to resize a partition on a grown LUN). This is somehow equivalent to adding a physical volume in a volume group under LVM. But contrary to LVM, once you added an extent to a VMFS, it is impossible to remove it.<\/p>\n<p>Well, until now, it was.<\/p>\n<p>I just pushed my <i>lvm<\/i> branch of vmfs-tools (get a <a href=\"http:\/\/git.glandium.org\/?p=vmfs-tools.git;a=snapshot;h=8eefcdc7c528c76b6a8f7d749eb5956b8d4d52e2;sf=tgz\">git snapshot tarball<\/a>), which includes a new tool named vmfs-lvm, allowing to just do that. For the moment, the tool is not cluster-safe, which means you'd better run it on an offline VMFS (i.e. make sure no server is using it). Data <i>should<\/i> not be at risk because the tool checks the removed extent doesn't contain any data, but it also assumes the filesystem is in a consistent state beforehand.<\/p>\n<p>The command line to remove an extent looks like the following:<\/p>\n<blockquote><p><code># vmfs-lvm extent0 extent1 ... extentn remove<\/code><\/p><\/blockquote>\n<p>This will remove the last extent.<\/p>\n<p><b>Update<\/b>: There was a bug when setting some values at volume level. The git snapshot link above has been updated accordingly.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Until vSphere 4, the only way to add space to an existing VMFS was to add an extent. This means creating a new partition, most of the time on a new LUN, and extend the VMFS there (vSphere 4 is now able to resize a partition on a grown LUN). This is somehow equivalent to [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[21],"tags":[23],"class_list":["post-513","post","type-post","status-publish","format-standard","hentry","category-vmfs-tools","tag-en"],"_links":{"self":[{"href":"https:\/\/glandium.org\/blog\/index.php?rest_route=\/wp\/v2\/posts\/513","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/glandium.org\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/glandium.org\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/glandium.org\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/glandium.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=513"}],"version-history":[{"count":6,"href":"https:\/\/glandium.org\/blog\/index.php?rest_route=\/wp\/v2\/posts\/513\/revisions"}],"predecessor-version":[{"id":619,"href":"https:\/\/glandium.org\/blog\/index.php?rest_route=\/wp\/v2\/posts\/513\/revisions\/619"}],"wp:attachment":[{"href":"https:\/\/glandium.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=513"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/glandium.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=513"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/glandium.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=513"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}