From owner-freebsd-stable Sat Jun 22 8:20:43 2002 Delivered-To: freebsd-stable@freebsd.org Received: from bolt.cx (bog515cdy240h.ab.hsia.telus.net [142.179.227.162]) by hub.freebsd.org (Postfix) with SMTP id BD30B37B404 for ; Sat, 22 Jun 2002 08:20:35 -0700 (PDT) Received: (qmail 90650 invoked from network); 22 Jun 2002 15:20:51 -0000 Received: from trinity.zero-gravity.org (HELO bolt.cx) (10.0.0.2) by neo.zero-gravity.org with SMTP; 22 Jun 2002 15:20:51 -0000 Message-ID: <3D1495D3.4030306@bolt.cx> Date: Sat, 22 Jun 2002 09:20:51 -0600 From: Chris Bolt User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: vinum problems continued Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm still having problems with vinum. A disk crashed and I replaced it, but I still can't get the volume back up. I created a new disk to replace the one that crashed: # cat /etc/vinum.conf.temp drive d2new device /dev/ad2s1e # vinum create /etc/vinum.conf.temp 3 drives: D d1 State: up Device /dev/ad1s1e Avail: 0/57239 MB (0%) D d3 State: up Device /dev/ad3s1e Avail: 0/57239 MB (0%) D d2 State: referenced Device Avail: 0/0 MB D d2new State: up Device /dev/ad2s1e Avail: 57239/57239 MB (100%) 1 volumes: V raid5 State: up Plexes: 1 Size: 55 GB 1 plexes: P raid5.p0 R5 State: degraded Subdisks: 2 Size: 55 GB 3 subdisks: S raid5.p0.s0 State: empty PO: 0 B Size: 55 GB S raid5.p0.s1 State: crashed PO: 0 B Size: 55 GB S raid5.p0.s2 State: empty PO: 1024 kB Size: 55 GB *** Warning: configuration updates are disabled. *** then I moved the crashed subdisk to the new drive: vinum -> move d2new raid5.p0.s1 *** Warning: configuration updates are disabled. *** vinum -> l 3 drives: D d1 State: up Device /dev/ad1s1e Avail: 0/57239 MB (0%) D d3 State: up Device /dev/ad3s1e Avail: 0/57239 MB (0%) D d2 State: referenced Device Avail: 0/0 MB D d2new State: up Device /dev/ad2s1e Avail: 0/57239 MB (0%) 1 volumes: V raid5 State: up Plexes: 1 Size: 55 GB 1 plexes: P raid5.p0 R5 State: degraded Subdisks: 2 Size: 55 GB 3 subdisks: S raid5.p0.s0 State: empty PO: 0 B Size: 55 GB S raid5.p0.s1 State: stale PO: 0 B Size: 55 GB S raid5.p0.s2 State: empty PO: 1024 kB Size: 55 GB But when I try starting it: vinum -> start raid5.p0.s1 Can't start raid5.p0.s1: Input/output error (5) *** Warning: configuration updates are disabled. *** vinum -> ls S raid5.p0.s0 State: empty PO: 0 B Size: 55 GB S raid5.p0.s1 State: R 0% PO: 0 B Size: 55 GB *** Revive of raid5.p0.s1 has stalled *** S raid5.p0.s2 State: empty PO: 1024 kB Size: 55 GB Hmm, maybe I have to fix the state? vinum -> setstate obsolete raid5.p0.s1 vinum -> start raid5.p0.s1 Can't start raid5.p0.s1: Device busy (16) *** Warning: configuration updates are disabled. *** What now? My on-disk configuration is at: http://www.bolt.cx/~chris/vinum/log /var/log/messages at: http://www.bolt.cx/~chris/vinum/messages /var/log/vinum_history at: http://www.bolt.cx/~chris/vinum/vinum_history -- Chris Bolt chris@bolt.cx http://www.bolt.cx/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message