SAP Knowledge Base Article - Preview

2864223 - Failed to start HANA due to "Disk quota exceeded" error.

Symptom

Failed to start HANA and there are errors related to space error from nameserver trace.

  • nameserver trace:

[9197]{-1}[-1/-1] 2019-11-13 05:59:38.782086 e FileIO SimpleFileAccessor.cpp(00166) : Could not open file "/usr/sap/XXX/HDB00/XXX/trace/nameserver_topology_XXX.json.new_XXX_9043_9197": 122 (Disk quota exceeded) with permissions rw-rw-r-- and flags 8
[9197]{-1}[-1/-1] 2019-11-13 05:59:38.782105 e TNS_Timing OfflineTopologyWriter.cpp(00040) : Error (122 (Disk quota exceeded)) while writing offline topology
.....

[13189]{-1}[-1/-1] 2019-11-13 06:01:16.583603 e FileIO LocalFileCallback.cpp(00344) : ERROR in async. file transfer: exception 1: no.2000008 (Basis/IO/FileAccess/impl/LocalFileCompletionThread.cpp:307)
Error during asynchronous file transfer (io_getevents), rc=28: No space left on device;


Read more...

Environment

  • SAP HANA 1.0, platform edition
  • SAP HANA, platform edition 2.0

Product

SAP HANA 1.0, platform edition ; SAP HANA, platform edition 2.0

Keywords

HANA, fail, Disk quota exceeded, No space left on device, writing offline topology , KBA , HAN-DB , SAP HANA Database , BC-OP-LNX-LENOVO , Linux on Lenovo hardware , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.