After Seamonkey browser crash, fsck_ffs is taking forever

Thomas Mueller mueller6724 at
Sat Apr 5 17:14:38 UTC 2014

My response at end, will not intersperse this time.

----- Original Message -----
From: Cary <cary at>
To: Thomas Mueller <mueller6724 at>; Users List <slackbuilds-users at>
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 * .
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 at  I too have made silly mistakes, including sending the wrong message.

I don't think * 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.


More information about the freebsd-questions mailing list