From owner-freebsd-current Fri Dec 6 8: 6:30 2002 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 AFEDB37B408; Fri, 6 Dec 2002 08:06:28 -0800 (PST) Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B8EB43E4A; Fri, 6 Dec 2002 08:06:25 -0800 (PST) (envelope-from ru@whale.sunbay.crimea.ua) Received: from whale.sunbay.crimea.ua (ru@localhost [127.0.0.1]) by whale.sunbay.crimea.ua (8.12.6/8.12.6/Sunbay) with ESMTP id gB6G67VX002642 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 6 Dec 2002 18:06:07 +0200 (EET) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.12.6/8.12.6/Submit) id gB6G63hr002633; Fri, 6 Dec 2002 18:06:03 +0200 (EET) Date: Fri, 6 Dec 2002 18:06:03 +0200 From: Ruslan Ermilov To: Petr Holub , Matt Dillon Cc: current@FreeBSD.org, mckusick@beastie.mckusick.com Subject: Re: UFS1 created by 5.0 is incompatible with 4.0's? Message-ID: <20021206160603.GB1058@sunbay.com> References: <004a01c29d27$45c2e0c0$2603fb93@kloboucek> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LpQ9ahxlCli8rRTG" Content-Disposition: inline In-Reply-To: <004a01c29d27$45c2e0c0$2603fb93@kloboucek> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --LpQ9ahxlCli8rRTG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 06, 2002 at 01:59:11PM +0100, Petr Holub wrote: > Hi, >=20 > > While testing the 4.0 -> 5.0 upgrade path, I've created (under > > 5.0) a UFS1 partition and installed 4.0 onto it. After booting > > the 4.0 from it, kernel complained about ``numdirs is zero, try > > using an alternate superblock'' for / partition -- I've tried > > what it suggests (by fsck -b 32, etc.) but the result was always > > the same -- the file system was marked dirty and only read-only > > usable. After rebooting in 5.0, this file system was similarly > > unusable. Is this a bug or a feature? >=20 > I've discussed this issue with Poul-Henning Kamp. You need fsck > from at least 4.7. >=20 Is this handled by fsck/setup.c,v 1.17.2.4 commit? : revision 1.17.2.4 : date: 2002/06/24 05:10:41; author: dillon; state: Exp; lines: +26 -56 : MFC 1.30. Check only the fields we know should be the same between the : primary and alternate superblocks, so fsck doesn't barf on new features : added to UFS in later releases. :=20 : Submitted by: mckusick Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --LpQ9ahxlCli8rRTG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE98MrrUkv4P6juNwoRAtW4AJ44LkhTbjMMQjY0XQs7eNWTqc2TmQCggGg0 tN+d6RXkbVHKSuzx6IJAEH4= =0SGd -----END PGP SIGNATURE----- --LpQ9ahxlCli8rRTG-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message