From owner-freebsd-questions@FreeBSD.ORG  Sat Jul 21 15:13:03 2012
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 6A3E01065672
	for <freebsd-questions@freebsd.org>;
	Sat, 21 Jul 2012 15:13:03 +0000 (UTC)
	(envelope-from freebsd@edvax.de)
Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14])
	by mx1.freebsd.org (Postfix) with ESMTP id 27AFA8FC1A
	for <freebsd-questions@freebsd.org>;
	Sat, 21 Jul 2012 15:13:03 +0000 (UTC)
Received: from r56.edvax.de (port-92-195-22-218.dynamic.qsc.de [92.195.22.218])
	by mx02.qsc.de (Postfix) with ESMTP id A00DC27C6F;
	Sat, 21 Jul 2012 17:06:14 +0200 (CEST)
Received: from r56.edvax.de (localhost [127.0.0.1])
	by r56.edvax.de (8.14.5/8.14.5) with SMTP id q6LF6EJS002244;
	Sat, 21 Jul 2012 17:06:14 +0200 (CEST)
	(envelope-from freebsd@edvax.de)
Date: Sat, 21 Jul 2012 17:06:14 +0200
From: Polytropon <freebsd@edvax.de>
To: Leslie Jensen <leslie@eskk.nu>
Message-Id: <20120721170614.6534450c.freebsd@edvax.de>
In-Reply-To: <500AC31C.4090204@eskk.nu>
References: <500ABECA.5010404@eskk.nu>
	<alpine.BSF.2.00.1207211643590.1598@wojtek.tensor.gdynia.pl>
	<500AC31C.4090204@eskk.nu>
Organization: EDVAX
X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl>,
	freebsd-questions@freebsd.org
Subject: Re: Power failure during portsnap fetch update
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Polytropon <freebsd@edvax.de>
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jul 2012 15:13:03 -0000

On Sat, 21 Jul 2012 16:56:28 +0200, Leslie Jensen wrote:
> Here are the errors:
> 
> 
> root@bsd01~:fsck -F /dev/ad4s3f
> ** /dev/ad4s3f (NO WRITE)
                  ^^^^^^^^

In that case, fsck won't correct any errors. Good for checking,
bad for repairing!

Make sure the partition isn't mounted (e. g. right after entering
SUM after a "boot -s" system start) and run:

	# fsck -yf /dev/ad4s3f

This will tell fsck to perform the check anyway (-f) and answer
YES (-y) to all questions regarding file system modification.
If you feel unhappy with this quite "brutal approach", leave
out the -y parameter and answer the questions yourself.

The error messages you did show in the form of

> MISSING '.'  I=5021  OWNER=root MODE=40755
> SIZE=512 MTIME=Jul 21 16:13 2012
> DIR=?
> 
> UNEXPECTED SOFT UPDATE INCONSISTENCY
> 
> FIX? no

and

> MISSING '..'  I=2571711  OWNER=root MODE=40755
> SIZE=512 MTIME=Jul 21 16:28 2012
> DIR=/ports/net/netselect
> 
> UNEXPECTED SOFT UPDATE INCONSISTENCY
> 
> FIX? no

as well as

> LINK COUNT DIR I=5021  OWNER=root MODE=40755
> SIZE=512 MTIME=Jul 21 16:13 2012  COUNT 1 SHOULD BE 2
> LINK COUNT INCREASING
> UNEXPECTED SOFT UPDATE INCONSISTENCY
> 
> ADJUST? no

show that the inodes of several directories have been damaged.
This perfectly fits your observation of not being able to
remove those directories.

You _need_ to repair the file system in order to proceed. First
let fsck try to do its job. If it fails to do so, attempt to
manually "repair" the inodes (by removing them altogether).




-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...