From owner-freebsd-current Mon Jul 29 9:26:27 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 1C86137B400 for ; Mon, 29 Jul 2002 09:26:26 -0700 (PDT) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id A42DB43E5E for ; Mon, 29 Jul 2002 09:26:25 -0700 (PDT) (envelope-from des@ofug.org) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 5187C535D; Mon, 29 Jul 2002 18:26:23 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: rob Cc: "current@freebsd.org" Subject: Re: Be careful mounting -stable partitions on -current References: <3D454C36.4E8C6AEF@pythonemproject.com> From: Dag-Erling Smorgrav Date: 29 Jul 2002 18:26:23 +0200 In-Reply-To: <3D454C36.4E8C6AEF@pythonemproject.com> Message-ID: Lines: 14 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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 rob writes: > I mounted my -stable /usr partition on -current /mnt to copy over a > kernel config file, and when I finally fired up -stable, the /usr > partition was borked. Fsck couldn't fix it manually. Luckily I had > backups. It said that the master record didn't match the alternate. I > might have rebooted without unmounting the -stable partition. There's nothing wrong with your partition, but there's a bug in your version of fsck. You can "fix" your partition with 'fsck -b 32 -y', but you really should update your system. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message