Date: Sat, 14 Sep 2002 11:38:33 +0930 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: Jaime Bozza <jbozza@thinkburst.com> Cc: stable@FreeBSD.ORG Subject: Re: vinum/softupdates/fsck strange problem Message-ID: <20020914020833.GG2474@wantadilla.lemis.com> In-Reply-To: <033401c25b30$07e65a90$6401010a@bozza> References: <033401c25b30$07e65a90$6401010a@bozza>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, 13 September 2002 at 9:15:36 -0500, Jaime Bozza wrote: > 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. The message means that there's something wrong with the contents of cylinder group 22, somewhere in the middle of the file system. It suggests that you have random corruption in the file system. > 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. 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? > 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. Greg -- See complete headers for address and phone numbers 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?20020914020833.GG2474>