From owner-freebsd-current Sun Mar 16 21:59: 0 2003 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 AD4B837B401; Sun, 16 Mar 2003 21:58:57 -0800 (PST) Received: from beastie.mckusick.com (beastie.mckusick.com [209.31.233.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEFEF43F75; Sun, 16 Mar 2003 21:58:56 -0800 (PST) (envelope-from mckusick@beastie.mckusick.com) Received: from beastie.mckusick.com (localhost [127.0.0.1]) by beastie.mckusick.com (8.12.3/8.12.3) with ESMTP id h2H1K7FL011951; Sun, 16 Mar 2003 17:20:07 -0800 (PST) (envelope-from mckusick@beastie.mckusick.com) Message-Id: <200303170120.h2H1K7FL011951@beastie.mckusick.com> To: Maxim Konovalov Subject: Re: 4.8-RC / 5-CURRENT UFS1 interoperability problem Cc: Ruslan Ermilov , Claude Buisson , current@FreeBSD.ORG In-Reply-To: Your message of "Thu, 06 Mar 2003 17:21:00 +0300." <20030306164251.Q86784@news1.macomnet.ru> Date: Sun, 16 Mar 2003 17:20:07 -0800 From: Kirk McKusick 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 Date: Thu, 6 Mar 2003 17:21:00 +0300 (MSK) From: Maxim Konovalov To: current@freebsd.org Cc: mckusick@freebsd.org Subject: 4.8-RC / 5-CURRENT UFS1 interoperability problem Hello, In short, there is a problem using the same UFS1 filesystem under -stable and -current. Please look at an attached typescript for details. I noticed a wrong superblock information either: [maxim@golf ~]$ df /spare Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s2a 22520288 -125476 20844144 -1% /spare Is it known bug? -- Maxim Konovalov, maxim@macomnet.ru, maxim@FreeBSD.org Executive summary: you need to run `fsck -f -p' whenever you switch to or from a 4.X (stable) and a 5.X (current) kernel. The reason is that the UFS1 superblock summary information is maintained in different parts of the superblock on these two systems. Neither system maintains the summary information used by the other. There is no risk of trashing your filesystem if you fail to run the fsck, but the information reported by `df' will be wrong until you run the fsck. Kirk McKusick =-=-=-=-=-=-= golf# uname -a FreeBSD golf.macomnet.net 4.8-PRERELEASE FreeBSD 4.8-PRERELEASE #19: Thu Feb 27 13:33:49 GMT 2003 root@golf.macomnet.net:/usr/obj/usr/src/sys/GENERIC i386 golf# fsck /dev/ad0s2a ** /dev/ad0s2a ** Last Mounted on /mnt ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 3 files, 3 used, 5630069 free (21 frags, 703756 blocks, 0.0% fragmentation) golf# mount /dev/ad0s2a /mnt golf# mount | grep mnt /dev/ad0s2a on /mnt (ufs, local, soft-updates) golf# exit exit - clean reboot golf# uname -a FreeBSD golf.macomnet.net 5.0-CURRENT FreeBSD 5.0-CURRENT #6: Wed Feb 19 10:01:22 MSK 2003 maxim@golf.macomnet.net:/usr/obj/usr/src/sys/GOLF5 i386 golf# fsck /dev/ad0s2a ** /dev/ad0s2a ** Last Mounted on /mnt ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups SUMMARY INFORMATION BAD SALVAGE? [yn] y SUMMARY BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? [yn] y 94155 files, 220230 used, 5409842 free (15210 frags, 674329 blocks, 0.3% fragmentation) ***** FILE SYSTEM WAS MODIFIED ***** golf# mount /dev/ad0s2a /mnt golf# mount | grep mnt /dev/ad0s2a on /mnt (ufs, local, nodev, noexec, nosuid, soft-updates) golf# exit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message