After Seamonkey browser crash, fsck_ffs is taking forever
erichsfreebsdlist at alogt.com
Sat Apr 5 12:01:53 UTC 2014
On Sat, 5 Apr 2014 04:43:00 -0700 (PDT)
Thomas Mueller <mueller6724 at bellsouth.net> wrote:
> Yahoo! Mail interface strongly favors posting entire response on top
> of message being responded to!
> Sorry if my format is a bit inelegant.
do not worry, at least I will not complain.
> On 3TB and a full copy under rsync? I would estimate up to three days.
> If you want to make a simple copy, use even things like cp -avp and
> you will get the copy much much faster.
> *My response: No! It was a partition of 140 GB, not the whole
> partition, but important subdirectories, and not including the 16 GB
> LiveUSB-OpenBSD image!
Should be done in a few hours.
> > This hard drive was bought late May 2011, now barely inside the
> > three-year warranty.
> Ok, test it after you have the copy and see how well it behaves.
> How about SMART?
> *I'll see if it's in FreeBSD ports and if so, build it for USB-stick
> install, maybe the USB 3.0 stick installation of FreeBSD 10.0-STABLE.
> Just searched on www.freshports.org and found
> sysutils/smartmontools. To work on BSD partitions, I'd want a
> FreeBSD version as opposed to Linux, Windows or anything else non-BSD.
SMART works directly with the drive. Just install it on the memory
stick and run it.
> *It's conceivable that I could have a loose connection or a bit of
> dust lodged in the part of the disk where the errors occur.
No dust. If dust would be the problem, you would have a very serious
problem. It is either a loose connection or a damaged cable if it is a
problem like this at all.
Connectors are normally able to seal gasses locally of. So, dust cannot
creep in at all.
> *On two occasions in this episode, system no longer recognized the
> hard drive, but it came back after powering off for 10 or 15 seconds.
Even this could be a thermal problem which in turn could be caused
by dust on the wrong place or a dying fan.
> > I would also very much like to know how to block annoyance web
> > domains such as *.doubleclick.net .
> *My response: How do you get 200 000 entries in /etc/hosts? Surely
> you don't type them all line-by-line?
Collecting and typing. There are some sample available at the Internet.
In addition I always kept my own entries. I never check if they got
> *I had even thought of getting IP addresses and directing
> ad.doubleclick.net to b.scorecardresearch.com IP address and vice
> versa, but with many more. Or maybe *.doubleclick.net to 127.0.0.1?
> Better than 10.0.0.x?
A connection to 127.0.0.1 will always be honoured while a connection to
any other address might will result in a time-out which would make
More information about the freebsd-questions