From owner-freebsd-questions@FreeBSD.ORG Tue May 4 08:44:54 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5E84F106568B for ; Tue, 4 May 2010 08:44:54 +0000 (UTC) (envelope-from antoniok.spb@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by mx1.freebsd.org (Postfix) with ESMTP id E04938FC1F for ; Tue, 4 May 2010 08:44:53 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id l26so1104518fgb.13 for ; Tue, 04 May 2010 01:44:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type; bh=YKXjSyGvXo3LIAETIEcCoJtpfiIn8j96wobNTpHonR8=; b=I36HepnJ30hc2IipySIfNobkhL7Qsdsld49wjtWo2R+0PBjTYkxzS7ie4hbD/a9TpR +o+ssjq6QKYsD6dtG7jiwEQF0INeCYynwGRmunVDx/wkQxTJQe3U/X2XZJr/rOlkDErg KquOPKjDQhaATVvB+8ix9FHNvsOwKCraR5O3g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=p43TdxCCGd5tyoWs/9bC4eilwW2l2lEbUtOfqyX9QCFrf8mwz5RXNHr/qm7yEYKd/T S2/KIO9QslEHtOjO6cvJZUuz8MSOCyEX9B4ySOZ5BfNDo5E3FaQROuyAP/Phl0HP7JWg qrjkTREH3h+hrI+3ss2IaDrM3bgig2QOxqb6Q= Received: by 10.239.174.15 with SMTP id h15mr921606hbf.105.1272962681367; Tue, 04 May 2010 01:44:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.239.192.69 with HTTP; Tue, 4 May 2010 01:44:21 -0700 (PDT) In-Reply-To: <4bdfdc4c.7uW1NWZG0Ilec22I%perryh@pluto.rain.com> References: <4bdfdc4c.7uW1NWZG0Ilec22I%perryh@pluto.rain.com> From: Antonio Kless Date: Tue, 4 May 2010 12:44:21 +0400 Message-ID: To: perryh@pluto.rain.com Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-questions@freebsd.org Subject: Re: Strange diskspace loss 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: Tue, 04 May 2010 08:44:54 -0000 2010/5/4 > wrote: > > > And the fsck: > > > > # fsck > ... > > ** /dev/aacdu0s1e (NO WRITE) > > ** Last Mounted on /var > > ** Phase 1 - Check Blocks and Sizes > > ** Phase 2 - Check Pathnames > > ** Phase 3 - Check Connectivity > > ** Phase 4 - Check Reference Counts > > UNREF FILE I=23587 OWNER=root > > MODE=100644 > > SIZE=0 MTIME=Apr 9 13:36 > > 2010 > > CLEAR? > > no > > > > UNREF FILE I=3156011 OWNER=root MODE=100644 > > SIZE=6944766 MTIME=May 4 04:34 2010 > > CLEAR? no > > > > UNREF FILE I=3179521 OWNER=www MODE=100644 > > SIZE=30361665474 MTIME=May 4 09:43 2010 > ^^^^^^^^^^^^^^^^ > > CLEAR? no > > There's at least part of your problem: 30GB that du can't see > because it isn't linked to by any directory entry. Something > associated with your web server has created a large scratch file, > which it still has open (and thus the space can't be reclaimed), > but it unlinked the file after creating it so that it would > automatically go away once the process dies. > > This sort of thing -- though seldom so large as this -- is not at > all uncommon in /tmp. It's less common, but (as in this case) not > unheard of, in /var/tmp. > So, in future, is there some sence to make /var, /var/log and /var/tmp on different partitions? I usually use only two - /var and /var/db/mysql on dedicated hard drive. -- Best regards, Antonio Kless, http://kless.spb.ru/