Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760003AbXENUO2 (ORCPT ); Mon, 14 May 2007 16:14:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757346AbXENUOQ (ORCPT ); Mon, 14 May 2007 16:14:16 -0400 Received: from mailer.gwdg.de ([134.76.10.26]:42842 "EHLO mailer.gwdg.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756412AbXENUOO (ORCPT ); Mon, 14 May 2007 16:14:14 -0400 Date: Mon, 14 May 2007 22:13:57 +0200 (MEST) From: Jan Engelhardt To: Dave Jones cc: Linux Kernel Subject: Re: tracking down disk spinups. In-Reply-To: <20070514185734.GM27604@redhat.com> Message-ID: References: <20070514185734.GM27604@redhat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Report: Content analysis: 0.0 points, 6.0 required _SUMMARY_ Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 713 Lines: 21 On May 14 2007 14:57, Dave Jones wrote: > >I was curious why my firewall box never spins down its disk. >Given it rarely writes stuff to logs, it's odd that it always >seems to have something to write out. >killing syslogd, and enabling /proc/sys/vm/block_dump >gets me a periodic spew in /proc/kmsg like.. Perhaps it would help if you use `fuser` to see who's got open files for read and/or write, then strace all processes and see who does reads/writes? Jan -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/