From owner-freebsd-questions@FreeBSD.ORG Sat Jun 23 10:57:40 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AC16710657D0 for ; Sat, 23 Jun 2012 10:57:40 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 139D88FC12 for ; Sat, 23 Jun 2012 10:57:39 +0000 (UTC) Received: from mart.js.berklix.net (p5DCBEEB5.dip.t-dialin.net [93.203.238.181]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id q5NAvX0q078277; Sat, 23 Jun 2012 10:57:34 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id q5NAvJvU013471; Sat, 23 Jun 2012 12:57:21 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id q5NAv1tF086046; Sat, 23 Jun 2012 12:57:07 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201206231057.q5NAv1tF086046@fire.js.berklix.net> To: Polytropon From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Sat, 23 Jun 2012 04:22:29 +0200." <20120623042229.c5d8a8d8.freebsd@edvax.de> Date: Sat, 23 Jun 2012 12:57:01 +0200 Sender: jhs@berklix.com Cc: "Leonardo M. =?ISO-8859-1?Q?Ram=E9?=" , Free BSD Subject: Re: fsck_ufs running too often X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jun 2012 10:57:40 -0000 > My suggestion: Set background_fsck="YES" in /etc/rc.conf and let > the system boot up that way. _If_ you have a faulty disk or other > data corruption, you'll notice this _before_ going multi-user and > maybe making things worse. Yes, it might take some time, but it's > time well invested in your data integrity. > > Alternative: Perform a "shutdown now" and go into single-user mode. > Then unmount all your file systems, do "mount -o ro /" and then > perform the fsck run on all file systems. It's typically adviced > to perform file system checks on unmounted (or at least read-only > mounted) file systems. man fsck: ----- Note that background fsck is limited to checking for only the most commonly occurring file system abnormalities. Under certain circumstances, some errors can escape background fsck. It is recommended that you perform foreground fsck on your systems periodically and whenever you encounter file-system-related pan- ics. --- So do a manual fsck to make sure there's no residual faults lurking. Realise fsck wont start if it thinks its clean, (but might not be clean) so Boot single user & type fsck or fsck -y PS /etc/rc.conf: fsck_y_enable="YES" # to regularly force clean if fsck asks # background_fsck="YES" # a trade off your decision Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, & indent with "> ". Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. Mail from @yahoo dumped @berklix. http://berklix.org/yahoo/