During restore using Commvault Simpana smdrd segfaults with Error 4

  • 7012205
  • 25-Apr-2013
  • 25-Apr-2013


Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 3
Novell Open Enterprise Server 11 (OES 11) Linux
Novell Open Enterprise Server 11 (OES 11) Linux Service Pack 1
CommVault Simpana / Galaxy 9.0.0 (BUILD84) (Support Pack 9a)


During a restore job performed using CommVault Simpana the Novell SMS smdrd daemon cores.

The stack of the core looks like:
#0  0xf744b6c0 in memchr () from /lib/libc.so.6
#1  0xf612bde9 in CFindD () from /opt/novell/lib/libtsafs.so.0
#2  0xf6114bd0 in TSunistrLLunistr () from /opt/novell/lib/libtsafs.so.0
#3  0xf60f3315 in GetNumberOfNodeNamesInTheUniPath () from /opt/novell/lib/libtsafs.so.0
#4  0xf60ce7bf in FS_Create () from /opt/novell/lib/libtsafs.so.0
#5  0xf610b77f in SetFileDirCharacteristics () from /opt/novell/lib/libtsafs.so.0
#6  0xf611129b in SIDF_DecodeNFSCharacteristics () from /opt/novell/lib/libtsafs.so.0
#7  0xf610392d in RestoreNFSCharacteristics () from /opt/novell/lib/libtsafs.so.0
#8  0xf6103fe9 in tsaRestoreThread () from /opt/novell/lib/libtsafs.so.0
#9  0xf61040db in SingleThread () from /opt/novell/lib/libtsafs.so.0
#10 0xf6104136 in StartJobRestore () from /opt/novell/lib/libtsafs.so.0
#11 0xf60fe037 in WriteDataSet () from /opt/novell/lib/libtsafs.so.0
#12 0xf772d86d in ?? () from /opt/novell/lib/libsmdr.so.0
#13 0xf77261de in ?? () from /opt/novell/lib/libsmdr.so.0
#14 0xf76fe4b9 in SMtgtrsp_ServiceIPC () from /opt/novell/lib/libsmdr.so.0
#15 0xf76f8424 in SMrsp_Respond () from /opt/novell/lib/libsmdr.so.0
#16 0xf76eac8a in SMchild_Main () from /opt/novell/lib/libsmdr.so.0
#17 0xf770da55 in w95oslib_ChildBegin () from /opt/novell/lib/libsmdr.so.0
#18 0xf764e4ab in start_thread () from /lib/libpthread.so.0
#19 0xf74a2d5e in clone () from /lib/libc.so.6


The resolution is threefold.

Until the fix in SMS is officially released, a FTF can be obtained trough Novell Technical Services.
The other part is to install CommVault SP9b, then add bCreateParentDir 1 in the OESDataAgent section of the registry.


During a restore, the initial sequence CommVault Simpana is using to restoring data, is first restore the files after that the parent directory.
Although the SMS smdrd daemon can handle this sequence it caused a severe error which triggered the smdrd to core.

Additional Information

The SMS daemon was adjusted to handle this sequence of restoring better and CommVault adjusted their agent so it can restore data in a more ideal sequence of first restoring the directory, then it's contents.