From owner-freebsd-questions@FreeBSD.ORG Thu Jun 16 11:24:15 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4BFDE1065687 for ; Thu, 16 Jun 2011 11:24:15 +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 B856F8FC26 for ; Thu, 16 Jun 2011 11:24:14 +0000 (UTC) Received: from park.js.berklix.net (pD9FBE218.dip.t-dialin.net [217.251.226.24]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id p5GBOCoj000225 for ; Thu, 16 Jun 2011 11:24:12 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by park.js.berklix.net (8.13.8/8.13.8) with ESMTP id p5GBOHpY056096 for ; Thu, 16 Jun 2011 13:24:17 +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 p5GBOC4v081952 for ; Thu, 16 Jun 2011 11:24:17 GMT (envelope-from jhs@fire.js.berklix.net) Message-Id: <201106161124.p5GBOC4v081952@fire.js.berklix.net> To: freebsd-questions@freebsd.org From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Wed, 15 Jun 2011 13:04:23 PDT." Date: Thu, 16 Jun 2011 13:24:11 +0200 Sender: jhs@berklix.com Subject: Re: how do i fsck my server? 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: Thu, 16 Jun 2011 11:24:15 -0000 Facts: 8.2-RELEASE man fsck -B ... 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 panics. /usr/src/sbin/fsck/ for specialist list discussion 8.2-RELEASE /usr/src/etc/defaults/rc.conf fsck_y_enable="NO" ; background_fsck="YES" My opinion: Some machines merit addition of /etc/rc.conf fsck_y_enable="YES" Machines where data is mastered elsewhere: (some http & ftp servers, routers, firewalls, name & boot & X servers, test boxes, laptops on day trips). Remote servers where a boot time interactive fsck "Shall I fix ?" , or failure to fix, could hang unreachably. ( If background_fsck="NO", more chance of interactive hang ) Some machines merit addition of /etc/rc.conf background_fsck="NO" For fuller fsck checking, examples: Machines with master copies of data. Laptops traveling for a week, where one can't return early to repair. One would avoid both fsck_y_enable="YES" & background_fsck="YES" if one has local access to console & wants (if necessary) to be able to break out of fsck & manually run fsdb. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; indent with "> "; Cumulative like a play script. Mail plain text: Not HTML, multipart/alternative, base64, quoted-printable.