Skip to main content
NetApp Knowledge Base

RDB instability post upgrade to 9.14.1P4

Views:
95
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:
6/14/2024, 3:41:24 PM

Applies to

  • ONTAP
  • RDB QUORUM

Issue

Post upgrade to 9.14.1P4, VLDB quorum becomes unstable. The following error messages can be seen:

  1. VLDB log:

Mon May 13 02:28:02 -0700 [lvsclus01-13: vldb: rdb.env.IOFailure:alert]: Error encountered in root volume I/O: Cannot rmdir '/mroot/etc/cluster_config/rdb/VLDB/_sql.save'; errno -1.

Mon May 13 02:28:02 -0700 [lvsclus01-13: vldb: rdb.env.IOFailure:alert]: Error encountered in root volume I/O: LU: Cannot backup the old database directory in epoch 67, failed to rename recon directory /mroot/etc/cluster_config/rdb/VLDB/_sql into /mroot/etc/cluster_config/rdb/VLDB/_sql.save, status FILE_IO_ERROR.

Mon May 13 02:28:02 -0700 [lvsclus01-13: vldb: ucore.panicString:error]: 'vldb: assertion (0) at src/rdb/sql_local_unit.cc:5680 failed, raising SIGABRT(6) at RIP 0x807d28a3a (pid 60057, uid 0, timestamp 1715592482)'

Mon May 13 02:28:13 -0700 [lvsclus01-13: spmd: spm.vldb.process.exit:EMERGENCY]: Volume Location Database(VLDB) subsystem with ID 60057 exited as a result of signal signal 6. The subsystem will attempt to restart.

  1. EMS LOG:

Error encountered in root volume I/O: Cannot rmdir '/mroot/etc/cluster_config/rdb/VLDB/_sql.save'; errno -1.

Error encountered in root volume I/O: LU: Cannot backup the old database directory in epoch 67, failed to rename recon directory /mroot/etc/cluster_config/rdb/VLDB/_sql into /mroot/etc/cluster_config/rdb/VLDB/_sql.save, status FILE_IO_ERROR.

'vldb: assertion (0) at src/rdb/sql_local_unit.cc:5680 failed, raising SIGABRT(6) at RIP 0x807d28a3a (pid 49764, uid 0, timestamp 1715582955)'

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.