Date: Mon, 30 Oct 1995 17:31:16 +1000 From: Stephen McKay <syssgm@devetir.qld.gov.au> To: Andreas Klemm <andreas@knobel.gun.de> Cc: freebsd-hackers@freebsd.org, syssgm@devetir.qld.gov.au Subject: Re: several diffs for dump(8) to display write throughput and such...c Message-ID: <199510300731.RAA09427@orion.devetir.qld.gov.au> References: <DH8J84.M6L@devetir.qld.gov.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Andreas Klemm <andreas@knobel.gun.de> wrote:
>The dump utility in Solaris 2.4 has the nice feature, to show the
>write throughput, when dumping to tape.
> DUMP: DUMP: 688558 tape blocks on 1 volumes(s)
>>>DUMP: DUMP: finished in 1451 seconds, throughput 474 KBytes/sec
> DUMP: level 0 dump on Sat Oct 28 20:28:29 1995
>***************
>*** 448,453 ****
>--- 449,457 ----
> else
> msg("DUMP: %ld tape blocks on %d volumes(s)\n",
> spcl.c_tapea, spcl.c_volume);
>+ msg("DUMP: finished in %d seconds, throughput %d KBytes/sec\n",
>+ tend_writing-tstart_writing,
>+ spcl.c_tapea/(tend_writing-tstart_writing)); /* AKL */
> putdumptime();
> trewind();
> broadcast("DUMP IS DONE!\7\7\n");
I can imagine cases where tend_writing == tstart_writing, causing a core dump.
This would be quite likely when testing dump scripts by dumping to a file or
/dev/null from a small filesystem.
Stephen McKay.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510300731.RAA09427>