Hi Renaud,
first: would you be able, in the future, to log a support case for such - well defined and well prepared, i.e. obvious - defect descriptions, just to allow for some bookkeeping and stuff around the work that's required?
I nonetheless proceeded and logged a defect for the onbar verification problem as I think both bar_dbug.log and psm_dbug.log provide sufficient information to understand the problem and, hopefully, get it fixed: some return code 3 is produced somewhere and propagated all the way up to BSAGetData() (for which it gets reported as "
A system error occurred.", corresponding to BSA_RC_ABORT_SYSTEM_ERROR (s.
https://pubs.opengroup.org/onlinepubs/9657499/chap4.htm) and ultimately ends up being onbar's return code.
What I'm not so sure about is whether your newly found restore problem is the same issue. Unfortunately all we really know about it is "
XBSA Error: (BSAGetData) Exceeded available resources." - which, at first glance, looks different (BSA_RC_NO_RESOURCES 0x13 = 19).
-> have you tried with lower debug level, or differing BAR_DEBUG / PSM_DEBUG levels, so at least some debug output can be gathered?
BR,
Andreas
------------------------------
Andreas Legner
------------------------------
Original Message:
Sent: Tue February 18, 2020 03:38 PM
From: Renaud Demarneffe
Subject: Backup in object store
Hello,
I just got to be able to reproduce the error during a restore but with the DEBUG level to 0.
2020-02-18 19:40:28.779457 3862 3860 Begin cold level 0 restore rootdbs (Storage Manager copy ID: 0 632).
2020-02-18 19:45:28.029499 3862 3860 88 percent of rootdbs has been restored.
2020-02-18 19:46:54.648648 3862 3860 XBSA Error: (BSAGetData) Exceeded available resources.
2020-02-18 19:46:54.648674 3862 3860 (-43391) Skipped backup/restore of space 'rootdbs'.
2020-02-18 19:46:55.422337 3862 3860 Unable to close the storage space restore: buc_fe.c : Archive API processing failed at line 684 for msgtype.
2020-02-18 19:47:00.422490 3862 3860 (-43140) Due to the previous error, logical restore will not be attempted.
I join the collected logs.
After that, I do a new restore with DEBUG level to 9 and it worked successfully. I also join the logs.
It's a very surprizing behaviours. Can the debug level have an influence on the result of a restore (do the traces slow down certain operations, making them run without error?) ?
Regards,
Renaud
------------------------------
Renaud Demarneffe
------------------------------