From owner-freebsd-performance@FreeBSD.ORG Sun Jun 6 09:51:03 2004 Return-Path: Delivered-To: freebsd-performance@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 256F316A4CE for ; Sun, 6 Jun 2004 09:51:03 -0700 (PDT) Received: from gw.lucenet.com.br (gw.lucenet.com.br [200.208.167.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id D539043D55 for ; Sun, 6 Jun 2004 09:51:01 -0700 (PDT) (envelope-from tec@mega.net.br) Received: from wipmail.com.br (gw.mega.net.br [201.0.9.38]) by gw.lucenet.com.br (8.12.9p2/8.11.3) with ESMTP id i56Gp6lx088002 for ; Sun, 6 Jun 2004 13:51:08 -0300 (BRT) (envelope-from tec@mega.net.br) Received: from 200.152.81.50 by matik.com.br (MDaemon.PRO.v6.8.5.R) with ESMTP id 24-md50000000168.tmp for ; Sun, 06 Jun 2004 13:16:51 -0300 From: TEC Meganet To: freebsd-performance@freebsd.org Date: Sun, 6 Jun 2004 13:50:34 -0300 User-Agent: KMail/1.6.2 References: <6.1.1.1.2.20040604170255.00bf3b38@cheyenne.wixb.com> <20040604222232.GB25234@Odin.AC.HMC.Edu> <20040604193547.6d69fa7f.wmoran@potentialtech.com> In-Reply-To: <20040604193547.6d69fa7f.wmoran@potentialtech.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200406061350.41312.tec@mega.net.br> X-Return-Path: tec@mega.net.br X-MDaemon-Deliver-To: freebsd-performance@freebsd.org X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-Spam-Processed: mega.net.br, Sun, 06 Jun 2004 13:16:52 -0300 Subject: Re: more on fsck with securelevel X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: tec@mega.net.br List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jun 2004 16:51:03 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi depending on what you are running on a server I had serious=20 performance impacts using fsck in the background (cache server/=20 e-mail) also it seems that fsck -p do not get all when running=20 slices with noatime and softupdate and the cache server was not=20 completly shut down before shutdown times out. cache or mail=20 partitions ever come up as dirty when not shutting the daemon=20 completly down before starting shutdown of the system to prefent eventual problems caused by fast shutdowns I ever set fsck=20 =2D -fy in rc on 4.9 On 5.x you can do so by setting in rc.conf background_fsck=3DNO and=20 fsck -fy in /etc/rc.d/fsck=20 You may lose some minutes on boot but get sure that your fs is clean I think that securelevel settings do not have to do with fsck since=20 it seems to be for [u]mount disks, rw access to mem and kmem and=20 module loading. Also fsck from rc is run before mount still as=20 single user. hans On Friday 04 June 2004 20:35, Bill Moran wrote: > Brooks Davis wrote: > > On Fri, Jun 04, 2004 at 05:05:34PM -0500, J.D. Bronson wrote: > > > I did set this in /etc/rc.conf: > > > fsck_y_enable=3D"YES" > > > > > > But I was wondering if this might be a good idea too: > > > (looking at the defaults) > > > > > > fsck_y_enable=3D"NO" # Set to YES to do fsck -y if the > > > initial preen fails. > > > background_fsck=3D"YES" # Attempt to run fsck in the > > > background where possible. > > > background_fsck_delay=3D"60" # Time to wait (seconds) before > > > starting the fsck. > > > > > > ..might it not be prudent to set 'background_fsck=3D"NO"' when > > > running in secure mode? > > > > > > Eventhough I shut down carefully, sometimes it still feels the > > > need to run fsck (even with soft updates)...but when running > > > securelevel, is it actually going to accomplish anything? > > > > I think just setting background_fsck_delay=3D0 may allow bgfsck to > > work. Once fsck has opened the FS, I think it should keep it > > open and writes should work. I'm not 100% sure of that though. > > fsck_y_enable determines what happens when a normal fsck fails.=20 > If it's set to "NO", you're dumped into single-user mode with a > scary message. If it's set to "YES", then fsck is rerun with the > -y option. Setting it to "YES" will allow the system to boot > automatically under almost all conditions, but you may lose data > that you could have recovered if you'd run fsck manually ... > assuming you know what you're doing well enough to recover that > data. > > background_fsck controls whether the initial boot fsck is run in > the background, after booting, or in the foreground during the > boot, forcing the boot process to wait on it (background_fsck=3D"NO" > is basically the same behaviour as pre-5 systems) > > background_fsck_delay is pretty obvious. > > Hopefully, that will help you reach a config that works for you. =2D --=20 WIPNET Telecom Ltda. (18)221.1615 (18)9111.1101 (18)9773.1053 GPG Public Key http://wip.mega.net.br/tec.asc Mensagens sem assinatura GPG n=E3o s=E3o nossas. Messages without GPG signature are not from us. =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAw0tfWdl37kGw7FQRAlqyAJwMHA32bygdAMOZBLntNXGqWPSUCQCaA6sS /PhxaigokppCAuZEAYXgwXg=3D =3D72Dw =2D----END PGP SIGNATURE-----