From owner-freebsd-questions@freebsd.org Mon Jul 10 17:39:31 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92A1ADAD242 for ; Mon, 10 Jul 2017 17:39:31 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay14.qsc.de (mailrelay14.qsc.de [212.99.163.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0310670835 for ; Mon, 10 Jul 2017 17:39:30 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay14.qsc.de; Mon, 10 Jul 2017 19:39:01 +0200 Received: from r56.edvax.de (port-92-195-70-185.dynamic.qsc.de [92.195.70.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 37A833CBF9; Mon, 10 Jul 2017 19:39:00 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v6AHcxpu005099; Mon, 10 Jul 2017 19:38:59 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Mon, 10 Jul 2017 19:38:59 +0200 From: Polytropon To: Matthias Apitz Cc: Subject: Re: Unusual Question Message-Id: <20170710193859.3841a624.freebsd@edvax.de> In-Reply-To: <4eff21f6-84f2-4cc5-8b92-b7e787be8853@unixarea.de> References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> <52627.76.193.16.95.1499645892.squirrel@cosmo.uchicago.edu> <20170710052228.GA2338@c720-r314251> <20170710090547.15ee3afc07c09955ba621ae1@sohara.org> <4eff21f6-84f2-4cc5-8b92-b7e787be8853@unixarea.de> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay14.qsc.de with 81560683BF7 X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1187 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 17:39:31 -0000 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. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...