VMware Cloud Community
tropix
Hot Shot
Hot Shot
Jump to solution

Extend or dont Extend a VMFS?

Hi all,

its a good pratice extend VMFS??

I began with two VMFS (vmfs01_storage and vmfs02_storage) of 100Gb.

When I need more space on VMFS, I create another LUN and extend the VMFS.

I'm now about 400Gb in both VMFS. I grow both VMFS extending 100Gb by time.

Could I have a issue with this pratice? Or its better create another VMFS?

Regards,

Eduardo

If you found this information useful, please consider awarding points for "Correct" or "Helpful".
0 Kudos
1 Solution

Accepted Solutions
admin
Immortal
Immortal
Jump to solution

Yes, power off the VM and do a cold migrate using VC if you have it, otherwise it's vmkfstools time.

View solution in original post

0 Kudos
11 Replies
esiebert7625
Immortal
Immortal
Jump to solution

It's generally not a good practice to extend a VMFS volume. It's better to migrate your VM's to another volume and create a new VMFS volume then migrate them back.

http://www.vmware.com/community/thread.jspa?messageID=61679

http://www.vmware.com/community/thread.jspa?messageID=323671񏁗

http://www.vmware.com/community/thread.jspa?messageID=604008&#604008

fyi...if you find this post helpful, please award points using the Helpful/Correct buttons....thanks

davidbarclay
Virtuoso
Virtuoso
Jump to solution

Agreed.

I won't use extents unless I am backed into a corner. Even then I will do it kicking and screaming with disclaimers Smiley Happy

Dave

0 Kudos
tropix
Hot Shot
Hot Shot
Jump to solution

So I have to create another VMFS volumes with 400Gb, and migrate all vmdk to new volumes?

Regards,

Eduardo

If you found this information useful, please consider awarding points for "Correct" or "Helpful".
0 Kudos
admin
Immortal
Immortal
Jump to solution

Yes, power off the VM and do a cold migrate using VC if you have it, otherwise it's vmkfstools time.

0 Kudos
kix1979
Immortal
Immortal
Jump to solution

Yup, but extents are another level of trouble best to avoid. It's a pain to migrate, but by far much less risk in the long run.

Thomas H. Bryant III
0 Kudos
sbeaver
Leadership
Leadership
Jump to solution

I also do not do extents except when there is no other choice. Now in ESX 2.x I just did not do them but in 3.0 I have 1 extent currently and although I was not happy about doing this I will say that it has been working well and also handled the SDRF replication test at our DR site perfectly also. So it is better in 3.x but try to avoid if you can

Steve Beaver
VMware Communities User Moderator
VMware vExpert 2009 - 2020
VMware NSX vExpert - 2019 - 2020
====
Co-Author of "VMware ESX Essentials in the Virtual Data Center"
(ISBN:1420070274) from Auerbach
Come check out my blog: [www.virtualizationpractice.com/blog|http://www.virtualizationpractice.com/blog/]
Come follow me on twitter http://www.twitter.com/sbeaver

**The Cloud is a journey, not a project.**
0 Kudos
kix1979
Immortal
Immortal
Jump to solution

In VI3 if you lose an extent you only lose the data on that volume, but since you cannot control where the files are placed it can be impossible to predict what will die.

Thomas H. Bryant III
0 Kudos
sbeaver
Leadership
Leadership
Jump to solution

Agreed and like I said it is just better in 3.x not anywhere near perfect just better then 2.x

Steve Beaver
VMware Communities User Moderator
VMware vExpert 2009 - 2020
VMware NSX vExpert - 2019 - 2020
====
Co-Author of "VMware ESX Essentials in the Virtual Data Center"
(ISBN:1420070274) from Auerbach
Come check out my blog: [www.virtualizationpractice.com/blog|http://www.virtualizationpractice.com/blog/]
Come follow me on twitter http://www.twitter.com/sbeaver

**The Cloud is a journey, not a project.**
0 Kudos
davidbarclay
Virtuoso
Virtuoso
Jump to solution

You're not 100% correct Kix, there is one guy who can predict what will die - Murphy!

Smiley Happy

Dave

0 Kudos
esiebert7625
Immortal
Immortal
Jump to solution

Also Father Time, everything eventually fails over time...MTBF

0 Kudos
kix1979
Immortal
Immortal
Jump to solution

Lol, thanks for the laugh

Thomas H. Bryant III
0 Kudos