From owner-freebsd-questions Tue May 4 12:11:20 1999 Delivered-To: freebsd-questions@freebsd.org Received: from sakaki.communique.net (sakaki.communique.net [204.27.64.202]) by hub.freebsd.org (Postfix) with ESMTP id 22C6D154E6 for ; Tue, 4 May 1999 12:11:15 -0700 (PDT) (envelope-from nectar@nectar.com) Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by sakaki.communique.net (8.8.8/8.8.8) with ESMTP id OAA00745; Tue, 4 May 1999 14:11:13 -0500 (CDT) Received: from spawn.nectar.com (spawn.nectar.com [10.0.0.101]) by cerebus.nectar.com (Postfix) with ESMTP id BAAFD38; Tue, 4 May 1999 14:11:11 -0500 (CDT) Received: from spawn.nectar.com (localhost [127.0.0.1]) by spawn.nectar.com (Postfix) with ESMTP id 651582072; Tue, 4 May 1999 14:11:02 -0500 (CDT) X-Mailer: exmh version 2.0.2 2/24/98 X-Exmh-Isig-CompType: repl X-Exmh-Isig-Folder: mlist/freebsd/questions X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-rsa.txt X-PGP-DSSfprint: AB2F 8D71 A4F4 467D 352E 8A41 5D79 22E4 71A2 8C73 X-PGP-DHfprint: 2D50 12E5 AB38 60BA AF4B 0778 7242 4460 1C32 F6B1 X-PGP-DH-DSSkey: http://www.nectar.com/nectar-dh-dss.txt From: Jacques Vidrine To: Greg Lehey Cc: freebsd-questions@freebsd.org In-reply-to: <19990504155450.U10134@freebie.lemis.com> References: <19990501210026.357911DC5@spawn.nectar.com> <19990502120821.W80561@freebie.lemis.com> <19990502070142.2AEF11DD7@spawn.nectar.com> <19990502163630.K80561@freebie.lemis.com> <19990502150018.1BA3D1DEB@spawn.nectar.com> <19990504155450.U10134@freebie.lemis.com> Subject: Re: vinum-- resizing disks Mime-Version: 1.0 Content-Type: text/plain Date: Tue, 04 May 1999 14:11:02 -0500 Message-Id: <19990504191107.651582072@spawn.nectar.com> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 4 May 1999 at 15:54, Greg Lehey wrote: [snip] > Were you able to get a dump? That would have interested me. > > Obviously I was wrong in thinking that Vinum would automatically > detect what was going on. It only half did. I'll have to take a look > at the code and fix it, but it won't be in the next week. > > I'll send you private mail about how to fix the situation. Unfortunately, it went from bad to worse from there. I've since had to blow away my machine and restore from backup. Here are some of the situations that I recevied panics or the system hung. This is just anecdotal -- I did not have a kernel with debugging compiled in, so I didn't collect any useful information. I hope that later I'll be able to setup a scratch machine to reproduce them. * I created a large volume, and shortly after the system hung during newfs. * I removed that volume and tried recreating it, and the system hung. * I ``resetconfig'', rebuilt all of my volumes, and restored my data. The system hung when I did the following: # mount /dev/vinum/rel /rel # cd /rel # umount -f /rel # fstat . No such file or directory: . # fstat .. [hung] [several file system trashed, presumbably because I had a lot of activity going on] * I ``resetconfig'', rebuild all of my volumes, and restore my data. I notice that I never initialized the second plex on any of my mirrored volumes (the second plex status was ``initializing'', and the subdisks of that plex were ``empty''), so I attempt a few things (``vinum start'', ``vinum init'') to try to get the second plex sync'd, and fail miserbly, destroying the filesystem in the process. I remove and recreate the volume, and notice that the sizes listed by ``vinum ld'' are again incorrect. * I ``resetconfig'', and rebuild all of my volumes. Before newfs'ing of my mirrored volumes (usr), I do ``vinum init usr.p1''. This seems to do the right thing, so I newfs it and restore my data. I decide to do a little more testing by detaching and reattaching the plex. I do ``vinum detach usr.p1'', which seems to work fine. I can't fsck or mount the volume afterwards, though (errors indicate that the volume doesn't contain a recognizable UFS). So I attempt to re-attach the plex using ``vinum attach ex-usr.p1 usr'' but get only ``Invalid argument'' That's stuff I remember, and I list it only in case some of the symptoms are recognizable to readers of this list. After I get some other work done, I'm going to try to reproduce some of these things and trap some debugging info. I shall also try a more current version of vinum (this is all 3.1-STABLE circa April 29). Later, Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message