Date: Mon, 10 Jul 2017 15:16:31 -0400 From: Mike Jeays <mj001@rogers.com> To: "freebsd-questions@FreeBSD. ORG" <freebsd-questions@FreeBSD.ORG> Subject: Fwd: Re: Unusual Question Message-ID: <ec00a0f6-21ca-7c40-a62b-7df60ed8071e@rogers.com> In-Reply-To: <156b5695-1cbf-c5fa-be49-ff52da58ba0f@rogers.com> References: <156b5695-1cbf-c5fa-be49-ff52da58ba0f@rogers.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17-07-10 01:38 PM, Polytropon wrote: > On Mon, 10 Jul 2017 17:36:19 +0200, Matthias Apitz wrote: >> The OP should just compile an own version of dd(1) which punches lets say >> every thousand blocks the current block number to see how far (or better >> how less) it will walk through before the kernel halts/crashes. > To extend this idea: > > I'd add a few continuous diagnostic messages (comparable to > the ^T status display), so when the SSH connection finally > drops, it's possible to see how far the dd process went. :-) > > > dd can be made to report its status by sending the kill command USR1. See man dd. You could send one every minute via cron.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ec00a0f6-21ca-7c40-a62b-7df60ed8071e>