From owner-freebsd-current@FreeBSD.ORG Thu Oct 7 16:55:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A6A216A538 for ; Thu, 7 Oct 2004 16:55:26 +0000 (GMT) Received: from clueful.shagged.org (clueful.shagged.org [212.13.201.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63BE043D1D for ; Thu, 7 Oct 2004 16:55:26 +0000 (GMT) (envelope-from chris@clueful.shagged.org) Received: from chris by clueful.shagged.org with local (Exim 4.40 (FreeBSD)) id 1CFbY0-00061A-4w; Thu, 07 Oct 2004 17:55:20 +0100 Date: Thu, 7 Oct 2004 17:55:20 +0100 From: Chris Elsworth To: Kris Kennaway Message-ID: <20041007165520.GA22942@shagged.org> References: <20041007110802.GA4960@shagged.org> <20041007133415.GA93146@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041007133415.GA93146@xor.obsecurity.org> User-Agent: Mutt/1.5.6i Sender: Chris Elsworth X-Shagged-MailScanner-Information: See www.mailscanner.info for information X-Shagged-MailScanner: Found to be clean X-MailScanner-From: chris@clueful.shagged.org cc: freebsd-current@FreeBSD.ORG Subject: Re: dump/mksnap_ffs & fsck failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 07 Oct 2004 16:55:26 -0000 On Thu, Oct 07, 2004 at 06:34:15AM -0700, Kris Kennaway wrote: > On Thu, Oct 07, 2004 at 12:08:03PM +0100, Chris Elsworth wrote: > > Hello all, > > > > Is this likely to be filesystem corruption in a really bad way, or a > > ufs bug: > > > > # /sbin/dump -0 -LuaC32 -f /backup/root.dump / > > mksnap_ffs: Cannot create //.snap/dump_snapshot: Input/output error > > > > # fsck_ufs /dev/mirror/gma > > ** /dev/mirror/gma (NO WRITE) > > ** Last Mounted on / > > ** Root file system > > ** Phase 1 - Check Blocks and Sizes > > fsck_ufs: cannot alloc 4294967292 bytes for inoinfo > > Why can't it write to the device? Is it mounted read-write? Drop it > to read-only and retry. Vice versa for the root filesystem; is it > mounted read-only? Ah, sorry, should have said - yes, the filesystem was mounted read-write (/dev/mirror/gma and / are the same thing), but it does the same thing in read-only: # init 1 .. # umount -a # mount -o ro / # mount /dev/mirror/gma on / (ufs, local, read-only) devfs on /dev (devfs, local) # fsck -y / ** /dev/mirror/gma ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes fsck_ufs: cannot alloc 4294967292 bytes for inoinfo Surely fsck doesn't really need 4GB of physical mem? There is 1GB of physical and 4GB of swap configured in this. -- Chris