Be careful mounting -stable partitions on -current
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. On my laptop (Sony FX290), each type of reboot has different consequences. reboot works as expected. CTRL-ALT-DEL does not- it syncs disks and then freezes. Shutdown -p now shuts down, but when you turn the laptop back on it freezes and you have to take the batteries out to get it working right again. Rob. (ps. this is the message I was trying to send that ended up as dozens of QUIT messages- sorry again) -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Be careful mounting -stable partitions on -current
rob wrote: 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... I'm told that the fsck on -stable has been updated to fix this problem. Have you updated your -stable machine recently? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Re: Be careful mounting -stable partitions on -current
At 7:18 PM + 7/29/02, [EMAIL PROTECTED] wrote: 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. The fix in question was to -stable, not -current (I am not sure if that was mentioned earlier). I think the change was committed to -stable sometime in early July, iirc. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Be careful mounting -stable partitions on -current
rob [EMAIL PROTECTED] 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 - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Re: Be careful mounting -stable partitions on -current
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 [EMAIL PROTECTED] To: rob [EMAIL PROTECTED] Sent: 29 Jul 2002 18:26:23 rob [EMAIL PROTECTED] 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 - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
