From owner-freebsd-fs@FreeBSD.ORG Tue Aug 14 21:47:18 2007 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4339C16A421 for ; Tue, 14 Aug 2007 21:47:18 +0000 (UTC) (envelope-from gore_jarold@yahoo.com) Received: from web63006.mail.re1.yahoo.com (web63006.mail.re1.yahoo.com [69.147.96.217]) by mx1.freebsd.org (Postfix) with SMTP id F2FB313C45D for ; Tue, 14 Aug 2007 21:47:17 +0000 (UTC) (envelope-from gore_jarold@yahoo.com) Received: (qmail 71886 invoked by uid 60001); 14 Aug 2007 21:47:16 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=js9XTknRCcgNXt3uYjiutkWXTidJNr1scy5lbsvPg6zQjyDPC8lyzTtFwweFAH6SAWf52Wfl+5BfXKo2+JXj5q27nIdzeHPSpbaCc/e7NsPOK0fUw8jpxVSVZjVzwe4jNPxMFALolyF11p8W8uWl2dPyzet3DDnqXbIityEywT0=; X-YMail-OSG: x3V68gwVM1lOmzVw58yuDpqtFtI4aLAUthwJuhSuVzfPoSxhzVcr5Y_HTcgr4R5y3KAZ8rPTEnsg8gxAp_PP0VKeEAGsXv1AK_j.LQf5uF49.Twr.5235I8loQGENPG. Received: from [71.63.232.32] by web63006.mail.re1.yahoo.com via HTTP; Tue, 14 Aug 2007 14:47:16 PDT Date: Tue, 14 Aug 2007 14:47:16 -0700 (PDT) From: Gore Jarold To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <924334.71021.qm@web63006.mail.re1.yahoo.com> Subject: Re: help needed - tuning a filesystem for rm and cp ? (more details) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2007 21:47:18 -0000 > > Here is a question for any and all out there reading > > ... what would you expect would happen to a system > > that was constantly maxing out this value, sometimes > > on a sustained basis, while the activity that caused > > it went on uninterrupted ? > > > > I am seeing the system halt ... is it reasonable to > > think that maxing that value out on a regular, > > sustained basis would cause a system to halt ? > > > > (6.2-release running on a 4 GB memory p4 xeon ... does > > nothing but fileserver duties) > > > If you have a lot of meta-data IO (which you seem to have), then it's > possible that the system is incredibly busy doing disk accesses, and > waiting on IO from storage. When you say 'halt' does that mean you > can't log in to it, and eventually it comes back alive, or does that > mean it is locked up in a way that never recovers? I never wait around to find out it it comes back ... It no longer responds to pings, so I assume it is actually crashed. Also, it should be noted that this system (and its large, >4TB filesystem) has quotas enabled. So perhaps a better question would be: Any comments on frequent, sustained maxing out of dirhash on a quota'd filesystem ? ____________________________________________________________________________________Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV. http://tv.yahoo.com/