Commit bae90fb9 authored by unknown's avatar unknown

BUG#20121 missing err msg for ENOSPC

getting BACKUP_FRAGMENT_REF in LQH from BACKUP would bail on
ndbrequire(false) instead of having good error message.

Can re-use error code from BACKUP as it's a FsRef error code,
which is NDBD_EXIT... except when it isn't.


storage/ndb/src/kernel/blocks/dblqh/DblqhMain.cpp:
  Report the correct error code on exit with failure to backup fragment (run LCP)
parent ed52ee88
...@@ -62,6 +62,7 @@ ...@@ -62,6 +62,7 @@
#include <signaldata/AttrInfo.hpp> #include <signaldata/AttrInfo.hpp>
#include <KeyDescriptor.hpp> #include <KeyDescriptor.hpp>
#include <signaldata/RouteOrd.hpp> #include <signaldata/RouteOrd.hpp>
#include <signaldata/FsRef.hpp>
// Use DEBUG to print messages that should be // Use DEBUG to print messages that should be
// seen only when we debug the product // seen only when we debug the product
...@@ -11434,7 +11435,17 @@ void Dblqh::execLCP_PREPARE_CONF(Signal* signal) ...@@ -11434,7 +11435,17 @@ void Dblqh::execLCP_PREPARE_CONF(Signal* signal)
void Dblqh::execBACKUP_FRAGMENT_REF(Signal* signal) void Dblqh::execBACKUP_FRAGMENT_REF(Signal* signal)
{ {
ndbrequire(false); BackupFragmentRef *ref= (BackupFragmentRef*)signal->getDataPtr();
char buf[100];
BaseString::snprintf(buf,sizeof(buf),
"Unable to store fragment during LCP. NDBFS Error: %u",
ref->errorCode);
progError(__LINE__,
(ref->errorCode & FsRef::FS_ERR_BIT)?
NDBD_EXIT_AFS_UNKNOWN
: ref->errorCode,
buf);
} }
void Dblqh::execBACKUP_FRAGMENT_CONF(Signal* signal) void Dblqh::execBACKUP_FRAGMENT_CONF(Signal* signal)
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment