From owner-freebsd-current@FreeBSD.ORG Mon Aug 8 01:49:04 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE09D106564A for ; Mon, 8 Aug 2011 01:49:04 +0000 (UTC) (envelope-from deeptech71@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 904968FC17 for ; Mon, 8 Aug 2011 01:49:04 +0000 (UTC) Received: by gxk28 with SMTP id 28so434892gxk.13 for ; Sun, 07 Aug 2011 18:49:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=UolHzncLfn1eGRfqfxldNp/rwLmM1H3ACaLSvN84lFI=; b=eBHapoEawYpQYYN0x/pkXYEviYK1aqMZwsuwbe2BQoWWrHzA8Z/tSUBYKIJqEx+Yd9 mq7/jkquQ6Wko3jaB9I5r6oLyLNlY1Oaf2is7UkYyFsxMRWJLMMyDFr3wXp0wuzyrzh7 vt8kv3OqwOII4ZOxTpBJqMwrhO5yyq+hxFPvU= MIME-Version: 1.0 Received: by 10.236.22.231 with SMTP id t67mr958289yht.30.1312768143708; Sun, 07 Aug 2011 18:49:03 -0700 (PDT) Received: by 10.236.60.162 with HTTP; Sun, 7 Aug 2011 18:49:03 -0700 (PDT) In-Reply-To: <4E3F1853.1040409@FreeBSD.org> References: <4E3F1853.1040409@FreeBSD.org> Date: Mon, 8 Aug 2011 03:49:03 +0200 Message-ID: From: "deeptech71@gmail.com" To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: ghost files X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2011 01:49:04 -0000 On Mon, Aug 8, 2011 at 12:57 AM, Doug Barton wrote: > On 08/06/2011 23:08, deeptech71@gmail.com wrote: >> i'd note that the hard drive is kind of old (>7 years), and i recently >> had the power cut during port build operations twice, although the >> (UFS) filesystem is fsck-clean. > > Have you actually booted single user and run 'fsck -y'? That should > probably be your next step. yes i have already done that. but just for show i double-checked again (single user mode, fsck -y), and the filesystem was reported to be clean.