From owner-freebsd-current@freebsd.org Thu Mar 22 06:26:23 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 06F58F6E417 for ; Thu, 22 Mar 2018 06:26:23 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (flets-sg1027.kamome.or.jp [202.216.24.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4BE93829C6 for ; Thu, 22 Mar 2018 06:26:21 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (kx.openedu.org [202.216.24.27]) by kx.openedu.org (8.14.5/8.14.5) with ESMTP id w2M6Q9KE061507; Thu, 22 Mar 2018 15:26:10 +0900 (JST) (envelope-from kiri@kx.openedu.org) Message-Id: <201803220626.w2M6Q9KE061507@kx.openedu.org> Date: Thu, 22 Mar 2018 15:26:09 +0900 From: KIRIYAMA Kazuhiko To: Thomas Steen Rasmussen Cc: KIRIYAMA Kazuhiko , freebsd-current@freebsd.org Subject: Re: ZFS i/o error in recent 12.0 In-Reply-To: <2deff4f0-6b97-7ccd-2763-8c812e871c78@gibfest.dk> References: <201803192300.w2JN04fx007127@kx.openedu.org> <2deff4f0-6b97-7ccd-2763-8c812e871c78@gibfest.dk> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.6 MULE XEmacs/21.4 (patch 22) (Instant Classic) (amd64--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 06:26:23 -0000 At Wed, 21 Mar 2018 08:01:24 +0100, Thomas Steen Rasmussen wrote: > > On 03/20/2018 12:00 AM, KIRIYAMA Kazuhiko wrote: > > Hi, > > > > I've been encountered suddenly death in ZFS full volume > > machine(r330434) about 10 days after installation[1]: > > > > ZFS: i/o error - all block copies unavailable > > ZFS: can't read MOS of pool zroot > > gptzfsboot: failed to mount default pool zroot > > > > FreeBSD/x86 boot > > ZFS: i/o error - all block copies unavailable > > ZFS: can't find dataset u > > Default: zroot/<0x0>: > > boot: > > Has this pool had new vdevs addded to it since the server was installed? No. /dev/mfid0p4 is a RAID60 disk of AVAGO MegaRAID driver[1]. > What does a "zpool status" look like when the pool is imported? Like below: root@t1:~ # zpool import -fR /mnt zroot root@t1:~ # zpool status pool: zroot state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 mfid0p4 ONLINE 0 0 0 errors: No known data errors root@t1:~ # [1] http://ds.truefc.org/~kiri/freebsd/current/zfs/dmesg.boot > > /Thomas > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > --- KIRIYAMA Kazuhiko