Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 15 Sep 2002 13:56:34 -0500
From:      "Jaime Bozza" <jbozza@thinkburst.com>
To:        "'Greg 'groggy' Lehey'" <grog@FreeBSD.org>
Cc:        <stable@FreeBSD.ORG>
Subject:   RE: vinum/softupdates/fsck strange problem
Message-ID:  <002501c25ce9$9c758cc0$6401010a@bozza>
In-Reply-To: <20020914020833.GG2474@wantadilla.lemis.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> > 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002501c25ce9$9c758cc0$6401010a>