VMware Cloud Community
kyfbof
Contributor
Contributor

Extended vmfs, but not all hosts see it

Hi there,

We created a datastore with three 50G luns. After scanning, all hosts

saw this 150G datastore. After adding few VMs on it, we decided to add

another 50G lun to this datastore. After scanning and refreshing, all

hosts recogized that this datastore has four 50G luns, but only host

that extended the datastore knows that it is now 200G ... the rest

still thinking that it is only 150G (see below and the attachments).

root@esxdev04 ROOT_HOME# vdf -h /vmfs/volumes/VolYaDevLB1

Filesystem Size Used Avail Use% Mounted on

/vmfs/volumes/4755772e-e48bfe79-e0ac-001c23c2f972 298G 186G 112G 62% /vmfs/volumes/VolYaDevLB1

root@esxDev01 volumes# vdf -h /vmfs/volumes/VolYaDevLB1

Filesystem Size Used Avail Use% Mounted on

/vmfs/volumes/4755772e-e48bfe79-e0ac-001c23c2f972 248G 186G 62G 74% /vmfs/volumes/VolYaDevLB1

root@esxdev02 ROOT_HOME# vdf -h /vmfs/volumes/VolYaDevLB1

Filesystem Size Used Avail Use% Mounted on

/vmfs/volumes/4755772e-e48bfe79-e0ac-001c23c2f972 248G 186G 62G 74% /vmfs/volumes/VolYaDevLB1

Did we miss an important step somewhere, or is there a patch for this

"unwanted feature?" Well, we booted the other hosts to fix the problem,

but I hope this is not the "important step" that I refer to.

Thanks in advance

Reply
0 Kudos
3 Replies
mcowger
Immortal
Immortal

Did you do a rescan on each of the other hosts?

--Matt VCDX #52 blog.cowger.us
Reply
0 Kudos
kyfbof
Contributor
Contributor

Yes. After that, the hosts can see that that datastore has four luns (captured in the attachments).

Reply
0 Kudos
kyfbof
Contributor
Contributor

Minor correction:

We increased from five to six luns. And since we 50G is our std when carving luns, we basically increase fr 250G to 300G. Finally, because there is a small portion of the disk used by ESX (probably as disk signature or disk header), the outputs are showing 248G and 298G instead.

Reply
0 Kudos