Talk:VMware VMFS

This is the talk page for discussing improvements to the VMware VMFS article.
This is not a forum for general discussion of the article's subject.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Article policies

Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL

Computing Low‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.

Reasons for changes[edit]

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)[reply]

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)[reply]

Corrections[edit]

I believe the line "Add or delete an ESX Server from a VMware VMFS volume without disrupting other ESX Server hosts." should be removed. Adding or removing access to a file system has nothing to do with the filesystem and nothing to do with the structure, features, or abilities of the file system. Cbreaker (talk) 04:59, 8 September 2008 (UTC)[reply]

"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)[reply]

Automatic discovery[edit]

The feature that new VMFS volumes are recognized "automatically" is not a filesystem feature, but rather a feature of the OS it is attached to. My Windows PC recognises memory cards when they are attached, but this is not a feature of the FAT filesystem or the memory card itself. If anything, it's a USB feature. (Lipatden (talk) 13:11, 22 July 2008 (UTC))[reply]

Logical unit numbers[edit]

I may not be following this exactly, but how does the numbering of the SCSI drives used by the filesystem affect the allocation of metadata, increasing the size of volumes, etc? This is rather confusing, and needs some explanation. 212.159.69.4 (talk) 12:38, 10 August 2011 (UTC)[reply]

Article needs updating VMFS 5 is available[edit]

Section title says it all ... 72.253.160.104 (talk) 20:39, 13 September 2011 (UTC)[reply]