From owner-freebsd-stable Sun Sep 15 11:59:32 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C35B37B400; Sun, 15 Sep 2002 11:59:30 -0700 (PDT) Received: from mail.thinkburst.com (juno.geocomm.com [204.214.64.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE2ED43E4A; Sun, 15 Sep 2002 11:59:29 -0700 (PDT) (envelope-from jbozza@thinkburst.com) Received: from mailgate.thinkburstmedia.com (gateway.thinkburstmedia.com [204.214.64.100]) by mail.thinkburst.com (Postfix) with ESMTP id BA650A950; Sun, 15 Sep 2002 13:59:52 -0500 (CDT) Received: from sigma.geocomm.com (sigma.geocomm.com [10.1.1.5]) by mailgate.thinkburstmedia.com (Postfix) with ESMTP id 7D5FA20F18; Sun, 15 Sep 2002 13:59:23 -0500 (CDT) Received: by sigma.geocomm.com (Postfix, from userid 805) id 743232453E; Sun, 15 Sep 2002 13:59:23 -0500 (CDT) Received: from bozza (dhcp00.geocomm.com [10.1.1.100]) by sigma.geocomm.com (Postfix) with ESMTP id 08AE72453C; Sun, 15 Sep 2002 13:59:23 -0500 (CDT) From: "Jaime Bozza" To: "'Greg 'groggy' Lehey'" Cc: Subject: RE: vinum/softupdates/fsck strange problem Date: Sun, 15 Sep 2002 13:56:34 -0500 Message-ID: <002501c25ce9$9c758cc0$6401010a@bozza> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 In-Reply-To: <20020914020833.GG2474@wantadilla.lemis.com> X-Sanitizer: ThinkBurst Media, Inc. mail filter 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 > > I'm not sure what happened to cause both of these systems to reboot, but > > they were sitting at single user with a softupdate inconsistency. The > > message that came up was: > > > > CG 22: BAD MAGIC NUMBER Ok, now that I know what the CG means, would it just be a coincidence that my cylinders per group (as per a warning with newfs) is also 22? I did a compare with a backup I made of the /var system and there was nothing different, so it's still pretty weird. Either way, I'm ok for now, but I'll watch for the error again. I wish I knew what caused the systems to reboot in the first place. > Without knowing the cause of the crash, it's impossible to say. Even > if you had a dump, it's not certain that it would help much. It could > be a hardware problem, it could be a software problem. Is there > anything in the log files which looks suspicious? Nothing at all. > > The only other thing that I noticed on both of these systems was > > that vinum was showing the disks as ad0h and ad2h instead of ad0s1h > > and ad2s1h. (The filesystems showed up correctly, though 'vinum ld' > > showed 100% free on both drives - rebooting fixed it) > > Hmm, that's a known problem with Vinum, but only after things have > gone wrong at some earlier point. You should take a look at > http://www.vinumvm.org/vinum/how-to-debug.html and check if you find > anything unusual. Will do. Like it said though, rebooting made it show the correct devices for the drives and I haven't seen the problem since. I'm building a new system from scratch here though, so I'll see if I can simulate some failures (and reboots) to see if I can get a similar error. Thanks! Jaime To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message