From owner-freebsd-mobile Mon Feb 12 15:49:37 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from hand.dotat.at (sfo-gw.covalent.net [207.44.198.62]) by hub.freebsd.org (Postfix) with ESMTP id 9D23837B491 for ; Mon, 12 Feb 2001 15:49:34 -0800 (PST) Received: from fanf by hand.dotat.at with local (Exim 3.20 #3) id 14SShc-000B9k-00; Mon, 12 Feb 2001 23:48:16 +0000 Date: Mon, 12 Feb 2001 23:48:16 +0000 From: Tony Finch To: Kevin Oberman Cc: mobile@freebsd.org Subject: Re: Any ideas on keeping the disk spun down on laptop Message-ID: <20010212234816.M35416@hand.dotat.at> References: <200102112211.f1BMBCL23187@ptavv.es.net> <20010212211351.F35416@hand.dotat.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010212211351.F35416@hand.dotat.at> Organization: Covalent Technologies, Inc Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Tony Finch wrote: >Kevin Oberman wrote: >> >>Has anyone looked into making update(4) not do any disk IO when there >>have been no changes to metadata? And, is there a way to extend the >>update period? Or am I completely off base in my belief that update(4) >>is the source of the continuing disk accesses. > >There is a simple patch to extend the time between syncer runs: see >PR#21859. I've been running with this for months now and it works >nicely. Regarding the other followups I should probably add that I don't mount my disks noatime and I leave atrun and cron on. The caveat of course is that you risk losing more data in the event of running out of battery power or whatever :-) Tony. -- f.a.n.finch fanf@covalent.net dot@dotat.at GERMAN BIGHT HUMBER: NORTHWEST 4 OR 5, BUT SOUTHWEST 5 IN SOUTH AT FIRST. RAIN AT FIRST. MODERATE BECOMING GOOD. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message