From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 1 21:00:46 2005 Return-Path: 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 1AF1516A41C for ; Wed, 1 Jun 2005 21:00:46 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5E1643D53 for ; Wed, 1 Jun 2005 21:00:45 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id j51L0fug021413; Wed, 1 Jun 2005 16:00:41 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <429E21E7.2000501@centtech.com> Date: Wed, 01 Jun 2005 16:00:23 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.7) Gecko/20050504 X-Accept-Language: en-us, en MIME-Version: 1.0 To: GiZmen References: <20050601182405.GA31071@procent.t2.ds.pwr.wroc.pl> In-Reply-To: <20050601182405.GA31071@procent.t2.ds.pwr.wroc.pl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2005 21:00:46 -0000 GiZmen wrote: > 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? I'm struggling with the same problem. Suggestion so far from Don Lewis: Try setting kern.maxdsiz to a larger value in /boot/loader.conf and rebooting. I've got mine set to 1GB. kern.maxdsiz="1073741824" This didn't do it for me, but it might work for you. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology A lost ounce of gold may be found, a lost moment of time never. ------------------------------------------------------------------------