From owner-freebsd-stable Fri Sep 13 7:18:15 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 0517537B400 for ; Fri, 13 Sep 2002 07:18:12 -0700 (PDT) Received: from mail.thinkburst.com (juno.geocomm.com [204.214.64.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42C8C43E8A for ; Fri, 13 Sep 2002 07:18:11 -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 ED4FEAE3A for ; Fri, 13 Sep 2002 09:18:47 -0500 (CDT) Received: from sigma.geocomm.com (sigma.geocomm.com [10.1.1.5]) by mailgate.thinkburstmedia.com (Postfix) with ESMTP id 483CE20F07 for ; Fri, 13 Sep 2002 09:18:10 -0500 (CDT) Received: by sigma.geocomm.com (Postfix, from userid 805) id 3BC4824543; Fri, 13 Sep 2002 09:18:10 -0500 (CDT) Received: from bozza (dhcp00.geocomm.com [10.1.1.100]) by sigma.geocomm.com (Postfix) with ESMTP id C4EE124542 for ; Fri, 13 Sep 2002 09:18:09 -0500 (CDT) From: "Jaime Bozza" To: Subject: vinum/softupdates/fsck strange problem Date: Fri, 13 Sep 2002 09:15:36 -0500 Message-ID: <033401c25b30$07e65a90$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 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Importance: Normal 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 searched the archives (as well as google) and can't seem to find anything about this particular problem. I'm running vinum in mirroring mode (based off of the Bootstrapping Vinum document) and last night I had a problem on two systems. One system was the /usr/home filesystem (never gets written to currently), the other system was the /var filesystem (rarely gets written to, web server that has very infrequest email and the assorted logging, but even then nothing at the time of the failures) 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 I searched the archives and couldn't find anything related. I looked through the fsck source and found a couple of locations dealing with this message, but was unsure as to what would have happened to cause the problem. Running fsck manually spewed out a ton of other errors (ran fsck -n first) so I attempted a forced mount. Forcing the mount, I checked all the "possibly written" areas (log files and such) and everything looked fine. I rebuilt the filesystem and things are fine now but I'm curious as to why this happened, especially on filesystems that shouldn't typically have that much (if any) volume. 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) Anyone have any ideas? Jaime Bozza To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message