From owner-freebsd-current@FreeBSD.ORG  Thu Oct  7 11:08:08 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 2433716A4CE
	for <freebsd-current@FreeBSD.ORG>;
	Thu,  7 Oct 2004 11:08:08 +0000 (GMT)
Received: from clueful.shagged.org (clueful.shagged.org [212.13.201.101])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E377643D4C
	for <freebsd-current@FreeBSD.ORG>;
	Thu,  7 Oct 2004 11:08:07 +0000 (GMT)
	(envelope-from chris@clueful.shagged.org)
Received: from chris by clueful.shagged.org with local (Exim 4.40 (FreeBSD))
	id 1CFW7v-0001NA-1C
	for freebsd-current@FreeBSD.ORG; Thu, 07 Oct 2004 12:08:03 +0100
Date: Thu, 7 Oct 2004 12:08:03 +0100
From: Chris Elsworth <chris@shagged.org>
To: freebsd-current@FreeBSD.ORG
Message-ID: <20041007110802.GA4960@shagged.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6i
Sender: Chris Elsworth <chris@clueful.shagged.org>
X-Shagged-MailScanner-Information: See www.mailscanner.info for information
X-Shagged-MailScanner: Found to be clean
X-MailScanner-From: chris@clueful.shagged.org
Subject: 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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2004 11:08:08 -0000

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

A machine with similar aged sources (this is 5.3B6) is fine, however.
The only differences I've made to sources are to apply
root_mount.patch from pjd.

Making snapshots and fsck'ing other filesystems (also in a gmirror)
works fine..

-- 
Chris