Talk:VMware VMFS
From Wikipedia, the free encyclopedia
[edit] Reasons for changes
Instead of simply changing, I want to document the changes and give the reasons here.
- SAN file system -> cluster file system: the file system normally not depends from the underlying protocol and access method. 'Cluster file system is the usual term for this.
- Added 'disadvantages' section, because there are some. —The preceding unsigned comment was added by Sophis (talk • contribs) 19:17, June 26, 2007 (UTC)
- Not sure why you would consider a limitation of 32 ESX hosts a disadvantage. It's a limitation but not really a disadvantage. —The preceding unsigned comment was added by 68.164.207.118 (talk • contribs) 03:54, June 30, 2007 (UTC)
-
- Yes, you're right. Disadvantage is a wrong word. --Sophis 22:08, 3 July 2007 (UTC)
Someone mentioned in the disadvantages section that the level of abstraction is provided by most SANs so VMFS is redundant. I don't think a SAN can provide file-level locking without a filesystem, which is the whole purpose of VMFS as far as I know. —Preceding unsigned comment added by 65.113.40.1 (talk) 13:47, 28 September 2007 (UTC)
[edit] Corrections
"extending a volume by growing a LUN is not supported" This is not true. When a LUN is grown, you can click on 'Add Storage' and select the new free space, which will add a new primary partition of VMFS and use it as an extent. After adding 3 extents, you'll have to manually convert the last partition to extended and add more, upto 32 extents are 'supported'.
"VMFS file systems are automatically recognized when new LUNs are discovered on SAN" Huh? They're only recognized if they exist on a LUN. A brand new blank LUN becomes available for creating a VMFS partition on. —Preceding unsigned comment added by 206.248.160.160 (talk) 02:59, 3 February 2008 (UTC)
