From owner-freebsd-current Thu May 23 12:45: 2 2002 Delivered-To: freebsd-current@freebsd.org Received: from sunic.sunet.se (sunic.sunet.se [192.36.125.2]) by hub.freebsd.org (Postfix) with ESMTP id BE6FC37B404 for ; Thu, 23 May 2002 12:44:56 -0700 (PDT) Received: from irfu.se (sol.irfu.se [130.238.30.6]) by sunic.sunet.se (8.9.3/8.9.3) with SMTP id VAA05561 for ; Thu, 23 May 2002 21:44:54 +0200 (MET DST) Received: from jet.irfu.se by irfu.se (SMI-8.6/SMI-SVR4) id VAA13529; Thu, 23 May 2002 21:44:07 +0200 Received: from localhost (yuri@localhost) by jet.irfu.se (8.11.6+Sun/8.11.6) with ESMTP id g4NJiqc25875 for ; Thu, 23 May 2002 21:44:53 +0200 (MEST) X-Authentication-Warning: jet.irfu.se: yuri owned process doing -bs Date: Thu, 23 May 2002 21:44:52 +0200 (MEST) From: yuri khotyaintsev X-Sender: yuri@jet To: current@FreeBSD.ORG Subject: Vinum problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! I had a vinum mirrored volume usr with two plexes usr.p0 and usr.p1, with respective subdisks usr.p0.s0 and usr.p1.s0. So recently one of the disks crashed. I tried to replace the disk with another one (which later appeared to be somewhat smaller) and run vinum create for a new disk. Because of the small size of the new disk vinum create exited with error, and after that usr.p1.s0 dissapeared from the vinum configuration. so now I have usr.p0 -> 1 subdisk (usr.p0.s0) usr.p1 -> 0 subdisk Volume usr shows status UP, but trying to run fsck on it produces a kernel panic. Any suggestions how should I proceed to avoid panic and mount the volume? I have no possibility to get new large disk now. Should I try to remove plex usr.p1 ? The system is 4.5-STABLE ___ Yuri Khotyaintsev Swedish Institute of Space Physics, Uppsala Division, Box 537, S-75121 Uppsala To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message