From owner-freebsd-hackers@FreeBSD.ORG  Wed Jun  1 18:24:10 2005
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
X-Original-To: hackers@freebsd.org
Delivered-To: freebsd-hackers@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D20D216A41C
	for <hackers@freebsd.org>; Wed,  1 Jun 2005 18:24:10 +0000 (GMT)
	(envelope-from gizmen@blurp.one.pl)
Received: from blurp.one.pl (blurp.t2.ds.pwr.wroc.pl [156.17.224.5])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8C40643D53
	for <hackers@freebsd.org>; Wed,  1 Jun 2005 18:24:10 +0000 (GMT)
	(envelope-from gizmen@blurp.one.pl)
Received: by blurp.one.pl (Postfix, from userid 1001)
	id EED5272F; Wed,  1 Jun 2005 20:24:05 +0200 (CEST)
Date: Wed, 1 Jun 2005 20:24:05 +0200
From: GiZmen <gizmen@zion.vsip.pl>
To: hackers@freebsd.org
Message-ID: <20050601182405.GA31071@procent.t2.ds.pwr.wroc.pl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
Cc: 
Subject: problem with file system
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2005 18:24:10 -0000

Hi,

Recently my box had a power failure and after reboot when
i wanted to check my encrypted filesystem with fsck i 
have that message:

# fsck /dev/ad0s1g.bde
** /dev/ad0s1g.bde (NO WRITE)
** Last Mounted on /crypto
** Phase 1 - Check Blocks and Sizes
 fsck_ufs: cannot alloc 2129430592 bytes for inoinfo

or:

# fsck_ffs -p /dev/ad0s1g.bde
/dev/ad0s1g.bde: NO WRITE ACCESS
/dev/ad0s1g.bde: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.


i know that i have no write access but this file system is 
mounted right now and it seems that everything is ok.
I have tried to repair this when this file system was unmounted
but i had the same errors.

I don't know how to repair this file system. Could anyone point me
what to do?

thx


-- 
Best Regards:
		GiZmen

UNIX is user-friendly; it's just picky about its friends
UNIX is simple; it just takes a genius to understand its simplicity