From owner-freebsd-questions@FreeBSD.ORG Thu Jul 19 11:10:32 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CFCBC1065672 for ; Thu, 19 Jul 2012 11:10:32 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [89.206.35.99]) by mx1.freebsd.org (Postfix) with ESMTP id 1D81C8FC19 for ; Thu, 19 Jul 2012 11:10:31 +0000 (UTC) Received: from wojtek.tensor.gdynia.pl (localhost [127.0.0.1]) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5) with ESMTP id q6JBAUMV015548 for ; Thu, 19 Jul 2012 13:10:31 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5/Submit) with ESMTP id q6JBAU2M015545 for ; Thu, 19 Jul 2012 13:10:30 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Thu, 19 Jul 2012 13:10:30 +0200 (CEST) From: Wojciech Puchar To: FreeBSD In-Reply-To: Message-ID: References: <201207190253.q6J2r3p0070058@mail.r-bonomi.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (wojtek.tensor.gdynia.pl [127.0.0.1]); Thu, 19 Jul 2012 13:10:31 +0200 (CEST) Subject: Re: fsck on FAT32 filesystem? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jul 2012 11:10:32 -0000 >> for very old drives it may not > > Would you be so kind as to point out the proof of that statement? sorry but i didn't save that article on hard drive. So no proof if you don't believe me i've actually read it. The main point is that you have - track - intra-track gap - finite precision of writing head positioning. When you write on track second time, head isn't positioned exactly as before so very thin stripe of previous recording remain. With sophisticated enough tools you may recover it, requiring like 10 times smaller head than normal. With modern drives size of magnetic domains are larger than this imperfection. If drive record properly this "stripes" of leftover recording are just too small to be stable. Even if it would, no hardware exist to do this, except maybe scanning electron microscope which would take years to scan whole surface of disk IMHO. Not sure if it can "see" surface magnetization as i don't precisely know how such microscope works. But i know it needs some time to scan even tiny thing. > Please provide an address or location where the documentation > supporting that statement can be found. By the way, "NOT READABLE" is > not equal to "UNRECOVERABLE". > yes i know the difference. Finally i am not sure if "bulk erases" can actually erase drives, for sure they can destroy disk electronics so disk appears cleared. The field needed to clear modern magnetic media are just enormous. They are enormous under normal operation of disk, but power is small as track width is defined in nanometers. If it would be my data to be erased i would just do dd if=/dev/zero of=disk bs=.. or if really paranoid then after this dd if=/dev/urandom of=disk bs=.. or if very paranoid then will just put that drives into fireplace, which would heat them over curie point which would definitely demagnetize whole media. more sure than bulk eraser, and definitely secure, for free.