From owner-freebsd-current@FreeBSD.ORG  Thu Oct  7 13:32:40 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 C437E16A4CE
	for <freebsd-current@FreeBSD.ORG>;
	Thu,  7 Oct 2004 13:32:40 +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 9F6DA43D1D
	for <freebsd-current@FreeBSD.ORG>;
	Thu,  7 Oct 2004 13:32:40 +0000 (GMT)
	(envelope-from kris@obsecurity.org)
Received: by obsecurity.dyndns.org (Postfix, from userid 1000)
	id 4FAA651449; Thu,  7 Oct 2004 06:34:15 -0700 (PDT)
Date: Thu, 7 Oct 2004 06:34:15 -0700
From: Kris Kennaway <kris@obsecurity.org>
To: Chris Elsworth <chris@shagged.org>
Message-ID: <20041007133415.GA93146@xor.obsecurity.org>
References: <20041007110802.GA4960@shagged.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="2oS5YaxWCcQjTEyO"
Content-Disposition: inline
In-Reply-To: <20041007110802.GA4960@shagged.org>
User-Agent: Mutt/1.4.2.1i
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
	<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 13:32:40 -0000


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

On Thu, Oct 07, 2004 at 12:08:03PM +0100, Chris Elsworth wrote:
> Hello all,
>=20
> Is this likely to be filesystem corruption in a really bad way, or a
> ufs bug:
>=20
> # /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

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?

Kris

--2oS5YaxWCcQjTEyO
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFBZUXWWry0BWjoQKURAtCQAKDXTLZw7s9y/Y4oaIz/VDNLmcoKHwCgqTlZ
RQq6ztN/aGnmIGMnCoFcew0=
=DJ35
-----END PGP SIGNATURE-----

--2oS5YaxWCcQjTEyO--