On Tue, Sep 15, 2020 at 03:19:25PM -0000, Stuart Henderson wrote:
> On 2020-09-15, Jose Soares <[email protected]> wrote:
> > Hi!
> >
> > I am getting the following output from dump:
> >
> > # dump -0au -f /dev/nrst0 /dev/rsd0d
> > DUMP: Date of this level 0 dump: Tue Sep 15 16:23:09 2020
> > DUMP: Date of last level 0 dump: the epoch
> > DUMP: Dumping /dev/rsd0d to /dev/nrst0
> > DUMP: mapping (Pass I) [regular files]
> > DUMP: mapping (Pass II) [directories]
> > DUMP: estimated 2843256661 tape blocks.
> > DUMP: Volume 1 started at: Tue Sep 15 16:24:11 2020
> > DUMP: Child 97414 returns LOB status 213
> >
> > Could you please explain the meaning of "LOB status 213"?
>
> LOB=low-order byte
>
> What 213 represents, I'm not sure...
The message comes from sbin/dump/tape.c
592 #ifdef TDEBUG
593 msg("Tape: %d; parent process: %d child process %d\n",
594 tapeno+1, parentpid, childpid);
595 #endif /* TDEBUG */
596 while ((waitingpid = wait(&status)) != childpid)
597 msg("Parent %d waiting for child %d has another
child %d return\n",
598 parentpid, childpid, waitingpid);
599 if (status & 0xFF) {
600 msg("Child %d returns LOB status %o\n",
601 childpid, status&0xFF);
602 }
213 is octal number (139, 0x8b) of exit code of child process.
As the status is &0xFF, I am not 100% sure, but usually an exit code
of 139 means that the process terminated due to receipt of signal 11,
and generated a coredump.
Do you have a dump.core file ? Can you extract the backtrace ?
Thanks.
--
Sebastien Marie
