VMware Cloud Community
Pflynn
Contributor
Contributor
Jump to solution

Block Size During Install

Hello,

I have a situation where there is a new build ver 4.0 server - local storage is 2.6 TB - I know local storage limits for any single drive is 2 TB, so I split it into 1 TB and 1.6 TB - However, in our old 3.5 way of doing things, I'd reformat the vmfs to a more appropriate block size than 1 MB. Now , however, the service console is already put in the first vmfs. So, should the best practice be to (a) size down the first vmfs to only accomodate the sc, or (b) is there another way of modifying the block size that I am not aware of?

Thanks for any/all assistance

Paul Flynn

0 Kudos
1 Solution

Accepted Solutions
depping
Leadership
Leadership
Jump to solution

As far as I'm aware there's currently no option to change the blocksize during the installation or afterwards. The best option would be to create a small disk on which the VMFS will reside for the Service console and create multiple or one large(depending on the size) LUN/Disk for the other VMFS volumes.

Duncan

VMware Communities User Moderator | VCP | VCDX

-


Blogging:

Twitter:

If you find this information useful, please award points for "correct" or "helpful".

View solution in original post

0 Kudos
7 Replies
AndreTheGiant
Immortal
Immortal
Jump to solution

The best idea is alway to format the VMFS later.

Both to be able to choose the right block size and both to be sure that disk alignment is well done.

PS: if possible create 3 virtual disk. One for ESX, and 2 (with < 2TB) for VMFS.

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Pflynn
Contributor
Contributor
Jump to solution

Hello,

Thanks for your response. I do usually reformat after, but the Service console is now stored there, so I cannot. Are you aware of any alternatives?

Best regards

Paul

0 Kudos
AndreTheGiant
Immortal
Immortal
Jump to solution

I do usually reformat after, but the Service console is now stored there, so I cannot.

Right. The first datastore could be a problem

Are you aware of any alternatives?

No idea... sorry.

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
Pflynn
Contributor
Contributor
Jump to solution

Ok, thanks

Paul

0 Kudos
depping
Leadership
Leadership
Jump to solution

As far as I'm aware there's currently no option to change the blocksize during the installation or afterwards. The best option would be to create a small disk on which the VMFS will reside for the Service console and create multiple or one large(depending on the size) LUN/Disk for the other VMFS volumes.

Duncan

VMware Communities User Moderator | VCP | VCDX

-


Blogging:

Twitter:

If you find this information useful, please award points for "correct" or "helpful".

0 Kudos
Pflynn
Contributor
Contributor
Jump to solution

OK thanks,

Since console is 8 GB, in terms of best practice, how much space should be allocated? IE do we need to allow for growth? I am guestimating....20 GB?

Merci,

Paul

0 Kudos
kaos
VMware Employee
VMware Employee
Jump to solution

Service Console min size requirement is around 9 GB. You can have a vmfs disk of 15 Gb and that should serve you good.

FWIW, if you forsee youself using the service console for a lot of things, you should plan your service console partitioning better i.e, accomodate extra space in /home , /tmp etc...create custom partitions as per your requirement.

0 Kudos