Another partitioning question....

[311bobby311]

So I have a different implementation that I am working on, I know that it is not 'optimal' however this is what the customer agreed to....

dell 2950, Dual Quad Core Xeon 2.33GHz, 1333 MHz FSB, 16GB 667MHz RAM, two 73GB 15k SAS drives in a RAID 1 (for the ESX OS)

Attached storage will be an Dell MD1000 with 6 146GB 15k SAS drives in a RAID 5 array

Note that there will be no HA (VMotion) and will pretty much be non-expansive.

My main question is for the partitioning for the ESX OS on the 2950.

It seems like a waste no to partition out the whole drive...

I know the some of the partitions have maximum limits to the size of the partition already.

So here is my semi-planned partition scheme, please critique

/boot 250

/ 4096 (or maybe making this like 20GB or bigger???)

swap 1024

/home 2048

/opt 2048

/tmp 2048

/usr 2048

/var 2048

vmkcore 100

I mean I have 73GB why not use it? or should I not use it......

:confused:

Thanks to anyone that even takes the time to read!!

[juchestyle]

73 gigs?

Just fill it up, all 73 gigs! Maybe add the swap size a little bigger, but I will sign off on this. But always get second opinions!

Respectfully,

[311bobby311]

I had the understanding that the swap partition is used differently in VI3 than in 2.x

so you didnt need to use as much for swap on the OS drives??

maybe im incorrect...

[Dave_Mishchenko]

By default the swap file is now located with the rest of the VMs and is created when the VM is powered on. It is equal to the size of memory that is allocated to the VM - the size of memory reservation.

You could always create a VMFS partition with the remaining space and use it for ISO storage, backups, etc.

[boydd]

You will still need a /swap for the console (2048 MB max).

DB

[311bobby311]

i do like the idea of using some of the 73GB as a vmfs

maybe have a 30GB '/' partition and the rest ~40GB as a vmfs

[juchestyle]

That sounds like a winning combination. That way you can store iso images, and other things you need for a successful VI3 implementation.

Respectfully,

Matthew