Error "THINPROV_NOSPACE: Backing pool for thin-provisioned LUN is out of space"
search cancel

Error "THINPROV_NOSPACE: Backing pool for thin-provisioned LUN is out of space"

book

Article ID: 318923

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • Hostd not responding due to out of space issue with thin-provisioned LUNs
  • The commands to the specific datastore\backing LUN may fail with the below-mentioned error in the vmkernel.log file. With time due to this kind of continuous error, the hostd of the hosts accessing this particular datastore will go to a not responding state and the host may get disconnected from VC.
Note: This error effectively means, the array has put the LUN in read-only mode and all writes are disallowed.
 
[Date]T19:25:12.313Z cpu3:2098856)ScsiDeviceIO: 3029: Cmd(0x459a906502c0) 0x2a, CmdSN 0x1a0d2b from world 0 to dev "[Device (naa/eui)]" failed H:0x0 D:0x2 P:0x8 Valid sense data: 0x7 0x27 0x7
 
Plugin Status: [0x8] THINPROV_NOSPACE: Backing pool for thin-provisioned LUN is out of space
Sense Key: [0x7] DATA PROTECT
Additional Sense Data: 27/07 SPACE ALLOCATION FAILED WRITE PROTECT


Environment

VMware vSphere ESXi 8.0
VMware vSphere ESXi 7.0
VMware vSphere ESXi 6.7
VMware vSphere ESXi 6.5
VMware vSphere ESXi 6.0

Cause

The main cause of this issue is that the LUN backing this datastore is thinly provisioned at the array and the pool where this LUN is part of is out of space and has entered Read-only mode.

Resolution

To resolve this issue, the space issue at the array side should be corrected. Make sure that the pool where this LUN is a part is provisioned with more or sufficient free space. For more information, see Thin-provisioned storage devices met soft threshold

Furthermore, please engage the storage vendor to check the condition of the impacted LUN/pool.