Date: Tue, 28 Jul 2009 16:21:05 -0500 From: Adam Vande More <amvandemore@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: fsck and dump freeze freebsd. any ideas? Message-ID: <6201873e0907281421x5fb5aeav60e0d6e4f83df492@mail.gmail.com> In-Reply-To: <20090728231610.9d7c9299.freebsd@edvax.de> References: <200907281407.13445.mirror176@cox.net> <20090728231610.9d7c9299.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 28, 2009 at 4:16 PM, Polytropon <freebsd@edvax.de> wrote: > On Tue, 28 Jul 2009 14:07:13 -0700, "Edward Sanford Sutton, III" < > mirror176@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 press Reset or Power off. Most cases of file system > corruption on hard reset or power loss are often repaired well by > the fsck program. (I had system crashes due to defective USB sticks > and never had file system corruption after a successful fsck run. > Note that I did fsck in the foreground.) > > If you cannot umount disks, run "sync" three or four times and wait > a little while. This is not "as good" as umounting disks, and quite > useless if the system is active (in terms of file I/O). > > > -- > Polytropon > >From Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... > > I've had fs corruption after a successful fsck runs, sometimes multiples are needed. I think after 2 consecutive runs it's as good as it's going to get, but I could be wrong more may be helpful. This is a rare occurrence in my experience. -- Adam Vande More
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6201873e0907281421x5fb5aeav60e0d6e4f83df492>