Date: 29 Jul 2002 18:26:23 +0200 From: Dag-Erling Smorgrav <des@ofug.org> To: rob <rob@pythonemproject.com> Cc: "current@freebsd.org" <current@freebsd.org> Subject: Re: Be careful mounting -stable partitions on -current Message-ID: <xzpbs8qh55c.fsf@flood.ping.uio.no> In-Reply-To: <3D454C36.4E8C6AEF@pythonemproject.com> References: <3D454C36.4E8C6AEF@pythonemproject.com>
next in thread | previous in thread | raw e-mail | index | archive | help
rob <rob@pythonemproject.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpbs8qh55c.fsf>