Date: Sun, 4 Nov 2012 17:47:59 GMT From: Christian Geier <catcher@lostpackets.de> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/173363: Panic on 'zpool replace' on readonly pool Message-ID: <201211041747.qA4HlxUW018658@red.freebsd.org> Resent-Message-ID: <201211041750.qA4Ho2YW018530@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 173363 >Category: misc >Synopsis: Panic on 'zpool replace' on readonly pool >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Nov 04 17:50:01 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Christian Geier >Release: 9.1-RC2 >Organization: >Environment: FreeBSD brutus.lostpackets.de 9.1-RC2 FreeBSD 9.1-RC2 #0 r241106: Mon Oct 1 18:26:44 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: I did a fresh install of FreeBSD 9.1-RC2 and imported an originally 4 disk zraid pool with only 3 disks attached in readonly mode (via zpool import -o readonly=on storage). On replacement of the missing disk via zpool replace storage ada1 the machine reboots instantly (with no messages in the system logs). I repeated the procedure five times with the same outcome. On importing the zpool without the readonly option, resilvering starts and works fine. >How-To-Repeat: Mount a degraded raidz with '-o readonly=on' and than do 'zpool replace poolname newdisk' >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201211041747.qA4HlxUW018658>