Dynamic Root Disk A.3.13 * Release Notes (766141-001, March 2014)

4 Known problems and workarounds
This chapter discusses the known issues and workarounds.
Out of memory issues
Issue
DRD clone or DRD sync fails with the following error when there are too many files in the root
volume group
ERROR: A fatal error has occurred in file usertasks/UserTask.cc.
Additional information:
Class and method where error happened: UserTask::runTask
Line number: 428
ERROR: Caught an unexpected std::exception.
Additional available information:
- The "SyncDRDSysUserTask" state machine was in the
"InactiveSysImgMountedState" state.
- The exception's what() value is: bad allocation exception thrown
- Please call the response center.
Workaround
The versions of DRD prior to A.3.13 support up to approximately 1 million files. DRD version
A.3.13 supports approximately 2.5 million files in the root volume group .
If there are more files in the root volume group than supported by DRD, the directories containing
large number of files must be excluded using -x exclude_list option or the files must be moved to
a volume group other than the root volume group.
DRD OE update issues
Issue
DRD runcmd update-ux fails with local source depots
When executing "drd runcmd update-ux" on the inactive DRD system image using a directory
depot (or mounted media) that resides on the active system image, the command fails with this
error:
ERROR: The expected depot does not exist at "<depot_name>"
Workaround
In order to use a directory depot on the active system image, you will need to install March 2010
or later versions of DRD, SWM, and SW-DIST products from an OE depot. This must be done
before the clone is created, so the new DRD, SWM, and SW-DIST are on the active system and
on the clone.
The following assumes the OE depot is at /var/depots/1003-DCOE. This must be executed as
root:
swinstall -x autoselect_dependencies=false -s /var/depots/1003-DCOE \
DRD SWM SW-DIST PHCO_36525
Out of memory issues 15