VMware Cloud Community
hidehara
Contributor
Contributor

Can't expand datastore capacity

Hi.

Please give me some advice.

I added HDD to storage for datastore "ds02" with LUN concatenation.

And I did "increase datasotre capacity" on vSphere client with Error.

The error is this.

"Unable to grow Filesystem, please see VMkernel log fordetails : No space left on device"

VMkernel log is this.

2014-11-06T01:59:05.584Z cpu38:34276)LVM: 2907: [naa.600000e00d280000002800c000010000:1] Device expanded (actual size 61160331231 blocks, stored size 30580164575 blocks)

2014-11-06T01:59:05.800Z cpu47:34276)LVM: 11172: LVM device naa.600000e00d280000002800c000010000:1 successfully expanded (new size: 31314089590272)

2014-11-06T01:59:05.977Z cpu47:34276)Vol3: 661: Unable to register file system ds02 for APD timeout notifications: Already exists

2014-11-06T01:59:05.980Z cpu47:34276)LVM: 7877: Using all available space (15657303277568).

2014-11-06T01:59:14.416Z cpu7:34276)LVM: 7785: Error adding space (0) on device naa.600000e00d280000002800c000010000:1 to volume 52f05483-52ea4568-ce0e-901b0e0cd0f0: No space left on device

2014-11-06T01:59:14.451Z cpu7:34276)LVM: 5424: PE grafting failed for dev naa.600000e00d280000002800c000010000:1 (opened: t), vol 52f05483-52ea4568-ce0e-901b0e0cd0f0: Limit exceeded

2014-11-06T01:59:14.451Z cpu7:34276)LVM: 7133: Device scan failed for <naa.600000e00d280000002800c000010000:1>: Limit exceeded

2014-11-06T01:59:14.451Z cpu7:34276)LVM: 7805: LVMProbeDevice failed for device naa.600000e00d280000002800c000010000:1: Limit exceeded

The results didn't increase capacity and missing divice on selecting device menu.

Adding capacity been recognized for vmfs,but not increase free capacity.

Of course shown datastore device at first time.

I did with vsphere client but from vsphere web client same.

Past capacity : 14.24TB

New capacity : 28.48TB(add 14.24TB)

vsphere 5.5(not update2)

I want to use new capacity.Give me advice.

Best regards.

Tags (3)
30 Replies
hidehara
Contributor
Contributor

Yeah,It's very strange.

Support vender says there are something error on VMFS.

They recommend "re"make ds02 datastore.

I have many VMs at ds02,and I try to expand because of no datastore space....

Reply
0 Kudos
Burak201110141
Enthusiast
Enthusiast

I can't say something because i didn't check your esxi environment but i recommend reboot esxi servers, move vms to another esxi with vmotion and restart...

------------------------------------------------------------------ http://burakvardar.wordpress.com
Reply
0 Kudos
Rubeck
Virtuoso
Virtuoso

If you bypass vCenter by connecting directly to the ESXi host using the vSphere Client, do you then see the same issue?

/Rubeck

Reply
0 Kudos
hidehara
Contributor
Contributor

Hello.

Thanks for reply.

I tried to connect directly and rescan all.

But same.I'm sad.

Reply
0 Kudos
hidehara
Contributor
Contributor

I'm grad to receive advice.

I propose ESXi host restart to my support vender.

I have 4 hosts and all hosts same.They say server restart effect is limited.

Reply
0 Kudos
landofopportuni
Contributor
Contributor

We ran into the same kind of issue couple of months back,where you have added an extent to the existing volume at the backend storage array but when you try to increase the  datastore  you can't see the extent . The solution for this is , you have to login (root) to one of the physical host in the cluster and then increase the datastore and it worked for us with out any hickups. But it seems like you have already added the extent to the existing datastore.

Correct me if I am wrong with any of my terminology.

CP22.JPG

extent.JPG

hidehara
Contributor
Contributor

Wow! Looks same!

VMware says there are "a few" same case in the world,and don't have resolution.

Because user don't hope resolve.Everyone do workaround,example datastore dell and make.It's faster than investigate and resolve.

I have 4 hosts and do rescan with connecting directly on all hosts.But not change.

I am trying that dell and make datastore .I send file system metadata to VMware for investigation.I want to know why.

Thanks a lot!

Reply
0 Kudos
landofopportuni
Contributor
Contributor

If you rescan the cluster for newer extents still it will not show the extent that you added in the backened array but if you login to one of the physical host in the cluster and do a quick re-scan it will show you the extent and then you can add it. Finally do a rescan for datastores at the cluster level and now every ESX host in that cluster will see the added extent.

Reply
0 Kudos
hidehara
Contributor
Contributor

Hi.

I did to dell datastore and add storage,but when creating VMFS occurred same error "no space left on device."

Now failed to add datastore became inactive state.

So I think the cause is storage data(include VMFS).

Next I want to try volume format in storage.

Reply
0 Kudos
SteveGalbincea
VMware Employee
VMware Employee

Same issue just happened to me at a client running ESXi 5.5 Build 3568722 - could not increase datastore size to match extent size until I logged in as root to one of the cluster hosts. This was in relation to an IBM V3700 SAN if that helps anyone figure out why this is happening.

Thanks for the tip @landofopportunities!

Steve

Reply
0 Kudos
abhishekrana9
Contributor
Contributor

I was facing a similar issue. I went to of the host with root credentials and from there extended the datastore and it worked.

Reply
0 Kudos