From owner-freebsd-stable Fri Oct 25 10:31:37 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2262F37B401 for ; Fri, 25 Oct 2002 10:31:36 -0700 (PDT) Received: from mtiwmhc11.worldnet.att.net (mtiwmhc11.worldnet.att.net [204.127.131.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5ACAE43E42 for ; Fri, 25 Oct 2002 10:31:35 -0700 (PDT) (envelope-from cswiger@mac.com) Received: from prime ([12.88.116.136]) by mtiwmhc11.worldnet.att.net (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with SMTP id <20021025173133.SHLA20156.mtiwmhc11.worldnet.att.net@prime> for ; Fri, 25 Oct 2002 17:31:33 +0000 Message-ID: <004b01c27c4c$60424630$0301a8c0@prime> From: "Charles Swiger" To: References: <3DB8228B.90203@vpop.net> <20021024201833.GA259@Deadcell.ant> <20021025044650.GA46167@dru.dn.ua> Subject: Re: fsck lasting several hours (and then forever) after crash Date: Fri, 25 Oct 2002 13:31:38 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Vladislav V. Zhuk wrote: [ ... ] > Every harddisk will be bad one day. fsck MUST be able to mark bad > blocks and recover residuary data on the disk. The purpose of 'fsck' is to make a filesystem consistent, not to do media surface testing. Modern hard drives usually already reallocate failing sectors to spare ones. Often, by the time hard media errors are reported back from the drive, the drive has run out of spare sectors and can no longer remap failing ones. This is also the point at which data starts being lost without much chance of recovery. > Or freebsd must have another tool for recover data from harddisk with bad blocks. Yes. You can copy the data from the failing drive to a new one via 'dd', and then fsck the new partition, which should then work fine. > Why under other OS it's a no problem?? "No problem" doing what? Testing the media? 'dd' will perform destructive read and write testing. A dump/restore cycle will perform read and write testing without losing the existing data. Test the validity of the backup, first. > (one week ago I recover FreeBSD data under M$ DOS. FreeBSD can't do anything > with partition with bad blocks, fsck even can't finish check). > Why other OS has tools for test surface HDD ?? Other people have addressed this. Note that the best disk-checking software for a given hard drive is probably the specific vendor utilities for that drive (typically MS-DOS based). > I like FreeBSD, but this OS absolutely don't ready for problem with > disks, that will come soon or late with every HDD !! Hard drives fail. Either you backup the data you care about, or you run the risk of losing data. > (I know about backup, RAID and other. I troubled by problem discovered > above). > > Sorry for my english. No problem. Certainly it's better than my {Russian,Polish,etc}... :-) -Chuck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message