Date: Mon, 8 Mar 2004 09:13:35 +1030 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: "George D. Gal" <ggal@vsecurity.com> Cc: freebsd-current@freebsd.org Subject: Re: kernel panic when mounting root vinum volume Message-ID: <20040307224335.GG67801@wantadilla.lemis.com> In-Reply-To: <027401c403f8$cafdcd20$5001a8c0@CINDY> References: <016a01c403af$001bf990$5001a8c0@CINDY> <20040306231234.GA67801@wantadilla.lemis.com> <027401c403f8$cafdcd20$5001a8c0@CINDY>
next in thread | previous in thread | raw e-mail | index | archive | help
--5lVNUoiW0yyvItcX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Saturday, 6 March 2004 at 23:00:55 -0500, George D. Gal wrote: > Hello Greg, > > Well, unfortunately I wasn't able to find the dot files you mention in the > documentation under /usr/src/sys/modules/vinum/.gdb* They're there in 4.9. For 5.2-CURRENT, read gdb(4). > I've tried this particular configuration under FreeBSD 5.2.1-REL and > 5.2-CURRENT and have the same problems under both. I'm using this > exact config on FreeBSD 4.9 without problems. I have not made > changes to the system source. > > My vinum list output is as follows: > 2 drives: > D d1 State: up /dev/ad1s1d A: 258/37122 MB (0%) > D d0 State: up /dev/ad0s1d A: 258/37122 MB (0%) > > 4 volumes: > V rootvol State: up Plexes: 2 Size: 2048 MB > V usrvol State: up Plexes: 2 Size: 12 GB > V varvol State: up Plexes: 2 Size: 10 GB > V datavol State: up Plexes: 2 Size: 12 GB > > 8 plexes: > P rootvol.p1 C State: up Subdisks: 1 Size: 2048 MB > P usrvol.p1 C State: up Subdisks: 1 Size: 12 GB > P varvol.p1 C State: up Subdisks: 1 Size: 10 GB > P datavol.p1 C State: up Subdisks: 1 Size: 12 GB > P rootvol.p0 C State: up Subdisks: 1 Size: 2048 MB > P usrvol.p0 C State: up Subdisks: 1 Size: 12 GB > P varvol.p0 C State: up Subdisks: 1 Size: 10 GB > P datavol.p0 C State: up Subdisks: 1 Size: 12 GB > > I've tried to also detach individual plexes to see if it would > eliminate the problem, without luck. What was the problem? Yes, you've said it, but you shouldn't expect people to go back and piece together the evidence. There's obviously a panic, but what else? > Unfortunately my vinum history and /var/log/messages has no error > messages or anything out of the ordinary for vinum or any other > errors for that matter. Let me decide whether things are out of the ordinary. > Since I have not yet setup the remote debug the details of the crash > are as follows. Where's the dump? > Right before the crash I see a message stating, configuration already read > from d1. > > running where in the debugger gives me the last few func calls: > > devsw > initdrive > read_drive_label > check_drive > vinum_scandisk > vinum_super_ioctl > vinum_ioctl What happened to the details? It's not easy to debug these problems. The least I could expect is your cooperation. Greg -- Note: I discard all HTML mail unseen. Finger grog@FreeBSD.org for PGP public key. See complete headers for address and phone numbers. --5lVNUoiW0yyvItcX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQFAS6WXIubykFB6QiMRAlX3AJsFVfR9TGmVU8Yjk019NDdI6qsaaQCcDT5R uhJVWPU4CeLOWwb/YewOT5Q= =pEif -----END PGP SIGNATURE----- --5lVNUoiW0yyvItcX--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040307224335.GG67801>