SQLVDI errorcode=(8); system halted
randyv
Posts: 166
Came in this morning and was greeted with unhappy users proclaiming our mission critical application unavailable. A quick check of SQL Monitor (shameless cross-post plug) revealed the server was unreachable.
Opened Vsphere and sure enough, the server was in the weeds. Restarted the server, then got the application back up. After catching up several failed jobs I had a look at the Event Viewer at the time the server went into the weeds.
At the root of several errors is this:
SQLVDI: Loc=BufferAreaManager::MapBuffers. Desc=Out Of Address Space. ErrorCode=(8)Not enough storage is available to process this command.
.Process=3968. Thread=2144. Server. Instance=MSSQLSERVER.
VD=Global\SQLBACKUP_AD755106-8329-4773-B26C-90C6F538F64D_SQLVDIMemoryName_0.
Now, I don't know what the 'address space' condition of the system was around 4:30 this morning when this error was thrown. Prior to this the log is clear of errors, so no indication of something going amiss.
As to being out of storage, there is 13.2 GB free on the root drive for the O/S to use, and on the SAN (NIMBLESTORAGE) there is over 172 GB free on the MDF volume and over 307 GB free on the LDF volume; so I cannot figure out the 'Not enough storage' issue unless 'storage' is memory.
Since the instance seems to include something about SQLBACKUP and since a Google of SQLVDI errors seems to indicate they are associated with backups I thought I'd post here to see if anyone had any insight into what we could do to prevent a re-occurrence.
Opened Vsphere and sure enough, the server was in the weeds. Restarted the server, then got the application back up. After catching up several failed jobs I had a look at the Event Viewer at the time the server went into the weeds.
At the root of several errors is this:
SQLVDI: Loc=BufferAreaManager::MapBuffers. Desc=Out Of Address Space. ErrorCode=(8)Not enough storage is available to process this command.
.Process=3968. Thread=2144. Server. Instance=MSSQLSERVER.
VD=Global\SQLBACKUP_AD755106-8329-4773-B26C-90C6F538F64D_SQLVDIMemoryName_0.
Now, I don't know what the 'address space' condition of the system was around 4:30 this morning when this error was thrown. Prior to this the log is clear of errors, so no indication of something going amiss.
As to being out of storage, there is 13.2 GB free on the root drive for the O/S to use, and on the SAN (NIMBLESTORAGE) there is over 172 GB free on the MDF volume and over 307 GB free on the LDF volume; so I cannot figure out the 'Not enough storage' issue unless 'storage' is memory.
Since the instance seems to include something about SQLBACKUP and since a Google of SQLVDI errors seems to indicate they are associated with backups I thought I'd post here to see if anyone had any insight into what we could do to prevent a re-occurrence.
What we do in life echoes in eternity <><
Randy Volters
Randy Volters
