Date: Sat, 16 Aug 2003 11:43:04 +0930 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: Dmitry Morozovsky <marck@rinet.ru> Cc: freebsd-stable@freebsd.org Subject: Re: vinum (root on vinum too) throw_rude_remark crash: endless loop Message-ID: <20030816021304.GQ8948@wantadilla.lemis.com> In-Reply-To: <20030812114228.M64103@woozle.rinet.ru> References: <20030811192306.E39447@woozle.rinet.ru> <20030812014822.GM803@wantadilla.lemis.com> <20030812110255.S64103@woozle.rinet.ru> <20030812114228.M64103@woozle.rinet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--Kuk/n493crKO4rgR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tuesday, 12 August 2003 at 11:57:14 +0400, Dmitry Morozovsky wrote: > On Tue, 12 Aug 2003, Dmitry Morozovsky wrote: > > DM> Now, for the source of panic. I *think* this is comething related to config > DM> consistency checker. BTW, what is proposed "correct" way to delete a volume? I > DM> was pushed to user 'rm -rf volname', and supposedly this was the problem; as > DM> far as I remember the config raght after crash recovery (unfortunately, I did > DM> not write it in details), there were volume intersection: That should work. > Well, I found this inconsistent configuration in serial console logs (luckily > me having freshly installed conserver-com! ;-) > > This will be rather long message, sorry. You should take a look at http://www.vinumvm.org/vinum/how-to-debug.html. There's a lot of stuff here that I don't need, and it's clouding the issues. > Also, vinum control program reported all disks as totally free! > vinum -> l > 6 drives: > D wd16-0b State: up Device /dev/ad0ds1a Avail: 0/511 MB (0%) > D wd16-1b State: up Device /dev/ad2ds1a Avail: 0/511 MB (0%) > D wd16-beta State: up Device /dev/ad2hs1a Avail: 152115/152115 MB (100%) > D seag80 State: up Device /dev/ad1hs1a Avail: 75806/75807 MB (100%) > D ibm60 State: up Device /dev/ad3hs1a Avail: 58131/58132 MB (100%) > D wd16-alpha State: up Device /dev/ad0hs1a Avail: 152115/152115 MB (100%) Well, only four of six. It would be nice to see how you got to this stage. > I removed p volume and then... > > vinum -> rm -rf p > vinum: removing p.p0 > vinum: removing p.p1 > vinum: removing p > vinum -> ld > 6 drives: > D wd16-0b State: up Device /dev/ad0ds1a Avail: 0/511 MB (0%) > D wd16-1b State: up Device /dev/ad2ds1a Avail: 0/511 MB (0%) > D wd16-beta State: up Device /dev/ad2hs1a Avail: 172595/152115 MB (113%) > D seag80 State: up Device /dev/ad1hs1a Avail: 96286/75807 MB (127%) > D ibm60 State: up Device /dev/ad3hs1a Avail: 78611/58132 MB (135%) > D wd16-alpha State: up Device /dev/ad0hs1a Avail: 172595/152115 MB (113%) > > as you can see, more than 100% free. Neat, huh? ;-) Yes, a bug. I must look at that more carefully. In the meantime, if you see this, it's a good idea to stop Vinum and restart it. After that, the values should be correct. > As a sidenote, there is another problem (hard to reproduce, no kernel dump > right now unfortunately) is panic with the following symptoms: > > Fatal trap 18: integer divide fault while in kernel mode I haven't seen this one, but it could be the result of incorrect available values in the printout above. > panic has been provoked via 'vinum ld' command, and I suppose it was > in free space/capacity calculations. Yes. Greg -- See complete headers for address and phone numbers --Kuk/n493crKO4rgR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE/PZMvIubykFB6QiMRAoA1AJ9T11x6Eb+h6QEyKAdi01eF1yLXawCZAfw1 1E9eZDvj5YWKOG83D+kXEUw= =UTNr -----END PGP SIGNATURE----- --Kuk/n493crKO4rgR--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030816021304.GQ8948>