From owner-freebsd-current@FreeBSD.ORG  Thu Oct  7 17:01:15 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 9EBF616A4CE
	for <freebsd-current@FreeBSD.ORG>;
	Thu,  7 Oct 2004 17:01:15 +0000 (GMT)
Received: from obsecurity.dyndns.org
	(CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 75CA643D41
	for <freebsd-current@FreeBSD.ORG>;
	Thu,  7 Oct 2004 17:01:15 +0000 (GMT)
	(envelope-from kris@obsecurity.org)
Received: by obsecurity.dyndns.org (Postfix, from userid 1000)
	id 63C895362F; Thu,  7 Oct 2004 10:02:51 -0700 (PDT)
Date: Thu, 7 Oct 2004 10:02:50 -0700
From: Kris Kennaway <kris@obsecurity.org>
To: Chris Elsworth <chris@shagged.org>
Message-ID: <20041007170250.GA4053@xor.obsecurity.org>
References: <20041007110802.GA4960@shagged.org>
	<20041007133415.GA93146@xor.obsecurity.org>
	<20041007165520.GA22942@shagged.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="pWyiEgJYm5f9v55/"
Content-Disposition: inline
In-Reply-To: <20041007165520.GA22942@shagged.org>
User-Agent: Mutt/1.4.2.1i
cc: freebsd-current@FreeBSD.ORG
cc: Kris Kennaway <kris@obsecurity.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
	<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 17:01:15 -0000


--pWyiEgJYm5f9v55/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Oct 07, 2004 at 05:55:20PM +0100, Chris Elsworth wrote:

> > > # /sbin/dump -0 -LuaC32 -f /backup/root.dump /
> > > mksnap_ffs: Cannot create //.snap/dump_snapshot: Input/output error
> > >=20
> > > # 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
> >=20
> > 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?
>=20
> 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:
>=20
> # 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
>=20
>=20
> Surely fsck doesn't really need 4GB of physical mem? There is 1GB of
> physical and 4GB of swap configured in this.

Perhaps it's trying to allocate a negative amount of memory (that
value is 2^32-4, or (unsigned int)(-4)), perhaps because it's failing
to check for an error condition and using the resulting negative
value.

Kris

--pWyiEgJYm5f9v55/
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)

iD8DBQFBZXa6Wry0BWjoQKURAvCNAJ0TXbSHQB5HAQuA3AsYeNhFQd/00gCg/pw/
PbE1NsA2tzzIQlc4HXSELoU=
=BQcK
-----END PGP SIGNATURE-----

--pWyiEgJYm5f9v55/--