Re: [Dump-users] Unable to handle removed files via incremental dumps

[Delian K. <kr...@kr...>]

On Friday 06 February 2004 16:39, Stelian Pop wrote:
> Are you perfectly sure you updated dump ? You use
> /usr/sbin/dump below, but my RPMS try to install
> /sbin/dump... Make sure you don't have several versions of dump
> on your disk.

[root@smtp0 tmp]# which dump
/usr/sbin/dump
[root@smtp0 tmp]# whereis dump
dump: /usr/sbin/dump /usr/share/man/man8/dump.8.gz
[root@smtp0 tmp]# rpm -q dump
dump-0.4b35-1

I've used rpm -Uvh, the old version is removed ...

> Hmm, really strange, the direct pipe should be the same as when
> going through cat/gzip. It alsa seems to crash after the full dump
> and restore has finished (
>
> I cannot see what is causing this. Try running the same command
> but with dump under strace -ff (strace -ff /usr/sbin/dump -1u...).
> Does this show something about the crash ?

You probably mean -fF here. I suspect the logs will be terribly
big if I'm tracing all the syscals(may be I'll shorten the output with
e.g. -e trace=3D..), but may be I'll try that also.

>
> Second thought: compile dump  with debug enabled and run it through
> gdb, then when it crashes use commands like "bt" to see where
> it happened.
>

Ok, I'll try that also.

> > One more question. What are these times that dump reports ?
>
> 54 minutes of real execution (clock time), 25 effective execution
> in algorithms, 36 seconrds in doing syscalls. Most of the time
> (53 minutes) was spend in waiting for the disk to be ready for read/wri=
te.
>
> See man 1 time and man 2 times for details.

I was not asking about the times "time" reports. I've asked about:
  DUMP: 32.57% done at 812 kB/s, finished in 0:20
  DUMP: 39.55% done at 657 kB/s, finished in 0:22
  DUMP: 52.02% done at 648 kB/s, finished in 0:18

Aren't these seconds, seconds of what ?

Regards,
Delian