Date: Sun, 15 Feb 1998 23:45:14 +0100 From: Ollivier Robert <roberto@keltia.freenix.fr> To: hackers@FreeBSD.ORG Subject: Re: VM messed: vm_page_free panic problem Message-ID: <19980215234514.36406@keltia.freenix.fr> In-Reply-To: <199802152139.OAA03239@usr01.primenet.com>; from Terry Lambert on Sun, Feb 15, 1998 at 09:39:57PM %2B0000 References: <19980215132713.12891@keltia.freenix.fr> <199802152139.OAA03239@usr01.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
According to Terry Lambert: > If an FS was mounted async, it could have been damaged beyond the > ability of fsck to repair it as the result of a crash. I do not In this case, the panic happen before any file system is mounted (except / but I do not mount / async). > spend time railing against async just because I like to hear myself > type. I do it because async is actually dangerous to FS integrity. I know that but have yet to lose one file since introduction of async mounts in FreeBSD. Even with /usr/src and the CVS repository async. > Ah. Compression. Disable your internal and external cache for the > time you are booting, and see if it fixes it. Also, do you have 48M? No, 64 MB. > Do you have a 3.0 installed? You should take the kernel from the Yes, I run CURRENT. I was just trying to recover from a stupid mistake (mount was compiled shared because when I "cvs co'ed" outside /usr/src, the NOSHARED option was not here) during my soft updates test. I just tumbled on the -- now -- known problem with the current bootdisks. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #0: Sat Feb 14 15:42:16 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980215234514.36406>