From owner-freebsd-questions@FreeBSD.ORG Sat Apr 5 20:27:05 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 042AB9AF for ; Sat, 5 Apr 2014 20:27:05 +0000 (UTC) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.230]) by mx1.freebsd.org (Postfix) with ESMTP id BCACFAA6 for ; Sat, 5 Apr 2014 20:27:04 +0000 (UTC) Received: from [72.132.160.201] ([72.132.160.201:54482] helo=ypsd.localhost) by cdptpa-oedge03 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 5E/E3-16704-71760435; Sat, 05 Apr 2014 20:27:03 +0000 Date: Sat, 5 Apr 2014 13:27:02 -0700 From: Cary To: Thomas Mueller , "freebsd-questions@freebsd.org" Subject: Re: After Seamonkey browser crash, fsck_ffs is taking forever Message-ID: <20140405202702.GA18249@ypsd.localhost> Mail-Followup-To: Thomas Mueller , "freebsd-questions@freebsd.org" References: <1396688223.7351.YahooMailNeo@web181004.mail.ne1.yahoo.com> <20140405163437.GA17605@ypsd.localhost> <1396717903.82481.YahooMailNeo@web181001.mail.ne1.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1396717903.82481.YahooMailNeo@web181001.mail.ne1.yahoo.com> User-Agent: Mutt/1.5.22 (2013-10-16) X-RR-Connecting-IP: 107.14.168.142:25 X-Cloudmark-Score: 0 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Apr 2014 20:27:05 -0000 On Sat, Apr 05, 2014 at 10:11:43AM -0700, Thomas Mueller wrote: > My response at end, will not intersperse this time. > > > ----- Original Message ----- > From: Cary > To: Thomas Mueller ; SlackBuilds.org Users List > Cc: > Sent: Saturday, April 5, 2014 4:34 PM > Subject: Re: After Seamonkey browser crash, fsck_ffs is taking forever > > On Sat, Apr 05, 2014 at 01:57:03AM -0700, Thomas Mueller wrote: > > > > Main hard drive is Western Digital Caviar Green 3 TB. > > > > How long should I let this continue?   > > > > > My suggestion would be to back up your data using a different tool than rsync and to wipe > your  partition and start over with a new FS even after the old FS has been marked clean > by fsck. > > > > > > I would also very much like to know how to block annoyance web domains such as *.doubleclick.net . > Yes, that is a good idea.  You should not need them, unless perhaps you are already > shopping for a new computer. > > > My response: > > Did you really mean to send your message to slackbuilds-users@slackbuilds.org?  I too have made silly mistakes, including sending the wrong message. > > I don't think *.doubleclick.net is a good way to shop for a new computer! > > What's bad about rsync?  Though I could make a new directory on the USB 3.0 hard drive partition, arlene-backup2 and use cp -Rpv on directories that I'd want to copy. > > But I don't want to back up everything, surely would not want to copy 16 GB LiveUSB-OpenBSD image, which was extracted from a .7z file.  Or DragonFlyBSD images. > > It looks like the bad blocks, or at least what NetBSD fsck_ffs shows, are around block number 740000000, rather than more widespread.  I won't let fsck_ffs continue indefinitely, considering it may be stuck in a loop.  I could newfs and copy back, or go with another partition on the same hard drive, or on USB 3.0 hard drive.  Using USB 3.0 hard drive has the disadvantage of immobilizing it; I would have to reboot to free the USB 3.0 hard drive for use with the other computer. > > I don't know if part of the hard drive has gone bad or if the file system was royally messed up.  It seemed two other frequently-used partitions had minimal damage and were brought back to health. > > Tom > Tom, Yes, my bad. :-( Posting to the other list was a silly mix-up, a result of using too many different muttrc files. rsync may not copy fast enough in emergency situations such as when a disk may fail. You have pax(1), tar(1), or cpio(1) to use instead. "cpio -p" with input from find (1) works well.