From owner-freebsd-hackers Fri May 14 5:17:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 8836615372 for ; Fri, 14 May 1999 05:17:16 -0700 (PDT) (envelope-from rminnich@acl.lanl.gov) Received: from localhost (rminnich@localhost) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id GAA691829 for ; Fri, 14 May 1999 06:17:11 -0600 (MDT) Date: Fri, 14 May 1999 06:17:11 -0600 From: "Ronald G. Minnich" To: hackers@freebsd.org Subject: superblock corruption Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG apropos the recent discussion on superblocks and whether they ever get corrupted, I just got a call from a friend. One of his cluster nodes had power-failed at a bad time, and fsck was indicating a superblock corruption problem. I told him about -b 32, which he had never had to use in four years of running a large cluster. This problem was so new to him that he in fact had never heard of the -b switch or the backup superblocks. He couldn't affort to lose what he had on this node, as he was in the middle of changing something and had not had a chance to back it up to a server. Backup superblocks are still a good idea, even when you only need them every few years. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message