From owner-freebsd-stable Fri Dec 14 9:28: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 20E8337B41A; Fri, 14 Dec 2001 09:27:58 -0800 (PST) Received: (from nsayer@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id fBEHRwk16604; Fri, 14 Dec 2001 09:27:58 -0800 (PST) (envelope-from nsayer) Date: Fri, 14 Dec 2001 09:27:58 -0800 (PST) From: Message-Id: <200112141727.fBEHRwk16604@freefall.freebsd.org> To: freebsd-stable@freebsd.org Subject: 4.4-RELEASE corrupting filesystems? Cc: mckusick@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG One of my machines has been prone to having one of its filesystems curdle for an unknown reason. I have ever only experienced 3 filesystems get curdled on FreeBSD ever, but all three were /usr filesystems on that one disk. The first time was a while ago, but now it's happened twice in the last week. This is (of course) a production machine, so I haven't had a lot of time to do detective work. The symptom is that the machine would either panic or hang, then on subsequent reboot it would report the superblock magic number wrong. Attempting to use an alternate superblock would basically result in the entire filesystem being thrown away. *This* time I am not going to turn soft-updates on to see if that helps. If anyone has any idea what is going on, I'd love to hear about it. I suspect there's something odd about this partition's setup, but have no idea what it might be. I don't necessarily even suspect softupdates, but turning them off seems like it would be a move in the direction of safety. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message