Date: Mon, 29 Jul 2002 19:18:15 UT From: rob@pythonemproject.com To: des@ofug.org Cc: freebsd-current@freebsd.org Subject: RE: Re: Be careful mounting -stable partitions on -current Message-ID: <200207291918.g6TJIGa61005@mmm1902.dulles19-verio.com>
next in thread | raw e-mail | index | archive | help
I cvsup'd on Friday of last week, after I restored /usr. Did the fix come later than that? I'm kind of afraid to try it again :) Thanks, Rob. >----- Original Message ----- >From: Dag-Erling Smorgrav <des@ofug.org> >To: rob <rob@pythonemproject.com> >Sent: 29 Jul 2002 18:26:23 > >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?200207291918.g6TJIGa61005>