You'd probably be better off asking in the Beta forum.. Just an FYI.

Local or SAN Disk?

DB

Ernst,

I'm not sure you can do this. Do you observe the following message in the vmkernel log file?

"Modification of active partition vmhbaX:X:X:X is not supported"

The message suggests that something else has the disk open. You didn't happen to have an fdisk session running on the disk at the same time that you were trying to create the VMFS volume?

Since ESX is not Linux, Linux fundamentals do not apply directly to this OS. CHogan is most probably right - the partition you are trying to extend your VMFS with, seems to be in use by the Service Console or by a VM. If you are using vmkfstools, make sure you are not supplying vmhbaX:Y:Z:0 as the device to be extended with. "0" corresponds to the entire disk, and the Service Console might have the disk open in case you have Service Console partitions on it.

ESX3.0 uses RHEL 3.0 for the Service Console OS. Remember that there are basically 2 operating systems running at the same time. There is RHEL 3 for the Service Console and then there is the ESX kernel, which is a proprietary OS kernel that is running to support the VM's. The Service Console is there to support and manage the ESX kernel so that you do not directly access it.

Hope this helps!