On 29 Jul 2009 , freebsd-questions-requ...@freebsd.org entreated
about
freebsd-questions Digest, Vol 269, Issue 6:
After one of the last crashes, the system would lock up a short time
after rebooting. I found the problem caused by background fsck locking
up the system. I took the partition
The smartctl tests on the three drives came back saying they were checked
100% without error; bad sectors have always caused an error and an aborted
scan at the point of trouble for me in the past.
I 'thought' I recalled seeing a panic along the lines of ffs_free or
something related to
After one of the last crashes, the system would lock up a short time after
rebooting. I found the problem caused by background fsck locking up the
system. I took the partition out of the startup check for now. I 'think' I
was installing a port during the last crash, but it has been a while.
On Tue, 28 Jul 2009 14:07:13 -0700, Edward Sanford Sutton, III
mirror...@cox.net wrote:
As a final question, is there any safe way to crash freebsd (or pull system
power) without a risk of filesystem corruption?
An easy way is to go into single user mode and umount all the
partitions, then
On Tue, Jul 28, 2009 at 4:16 PM, Polytropon free...@edvax.de wrote:
On Tue, 28 Jul 2009 14:07:13 -0700, Edward Sanford Sutton, III
mirror...@cox.net wrote:
As a final question, is there any safe way to crash freebsd (or pull
system
power) without a risk of filesystem corruption?
An
