From owner-freebsd-fs@freebsd.org Tue Nov 8 18:18:52 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 95DB7C37C1C for ; Tue, 8 Nov 2016 18:18:52 +0000 (UTC) (envelope-from jacques.fourie@gmail.com) Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5075A15B for ; Tue, 8 Nov 2016 18:18:52 +0000 (UTC) (envelope-from jacques.fourie@gmail.com) Received: by mail-vk0-x229.google.com with SMTP id x186so155926656vkd.1 for ; Tue, 08 Nov 2016 10:18:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=qGf/KF9x79CVFbrfFNKDeal/6Rc2KnyxT4peSb05o0c=; b=0NgAArNcwkS42BNY89U3VAoobJ1T5DyOKk/T6xQ0xeV6M1Ggpp9ReTVjIbSh7pA4sA 1IvSQ/R4FHGrnFJcE7vgYG6cv9zXM1IYr5vwQTaUkSx9wtCnwigVfAY90gmEkkLQobwx p7hyDsDVABCtumEHYvrAyN5KlztjXcGe42jwjI8f34Hs9yAmlmnGKVmLZcjcwqU0xdLI XwitmKKnSPSzTfK5vBnYOHT7p71mp/APkEwkP2pnYrPysbWc1o9O9K2hdjIrESDSvYFq Sdo1iIFN/eMPK8e50iQXcLPw6ki8qH+6Z4dVVcujkIql/9czIRV1FaOdNqzVe6FW+ZO/ QxAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=qGf/KF9x79CVFbrfFNKDeal/6Rc2KnyxT4peSb05o0c=; b=ZfiQ3btqs/afMigghvhv8ylnAFMI+b9WaOLQgrE62149CS3j4M+iAfdMYRL8p8Z6ws DqEwGQGo9ugk/028B4ydK/5Lw8cRL24cLsL4c6Ar8SjkO0bOKDWtWmy6eypteO4LCoG6 VQoZX1uHliKtsxU6DAGdaERok0uJlUpBf6LK3igbInZzemuinj4boESf9qfEDsgX4iXx I59wgKrPr9818BjPunDPbA+GD+QZTBrT4YuCxZedoEThl/fdEaxVHtfDfLTi5BV1fR3u Z6wlqPHPjZg3lZVYclHutol+hZOTvm0ZWXac8NrHndGIc6xyE1bqtzM8O/UHiMf16J00 W18A== X-Gm-Message-State: ABUngvdEij/9hHDa+r+lffHUa8aBvBvqZyOH5GXgaP7E+DqCbZpn0XE96oZLhgvMuw5cRgEc8AdKSv9rN8Va8g== X-Received: by 10.31.163.4 with SMTP id m4mr7957297vke.176.1478629131389; Tue, 08 Nov 2016 10:18:51 -0800 (PST) MIME-Version: 1.0 References: <5521603a-65ef-7b79-4fa8-4315e1d9c7f8@unice.fr> In-Reply-To: <5521603a-65ef-7b79-4fa8-4315e1d9c7f8@unice.fr> From: Jacques Fourie Date: Tue, 08 Nov 2016 18:18:41 +0000 Message-ID: Subject: Re: FreeBSD 11.0 + ZFSD To: Jean-Marc.LACROIX@unice.fr, freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2016 18:18:52 -0000 9other. eh6 On TkhzKMVV CCV.,a.ue, Nov 8, 2016, 11:34 yyyyyyAM wrngbte: > Hello, > > We are testing the mecanism of ZFSD on the latest FresBSD 11.0. In > order to do that, > we have created a VMware virtual machine with 5 disk: > - 1 disk for the system OS > - 3 disks for the raidz1 pool > - 1 disk for spare > > So modified /etc/rc.conf to have the daemon start at boot, and rebooted. > > Then (in the the virtual machine parameters, to simulate a disk failure) > we removed a disk of the pool > We can see that ZFSD proceed to the replacement of the UNAVAILABLE disk > by the spare disk. > and complete the resilver. > Then, we removed (in the the virtual machine parameters) a second disk > of the pool > =3D> the pool is marked as UNAVAIL, if we try, for example, to cd to a > filesystem in the pool, > it crashed completely, we have to kill the terminal, and reconnect the > server. > > But if we issue a zpool clear zpool command, The pool status change > state from UNAVAIL to DEGRADED as shown below: > > root@pcmath228:~ # zpool status > pool: zpool > state: DEGRADED > status: One or more devices has experienced an error resulting in data > corruption. Applications may be affected. > action: Restore the file in question if possible. Otherwise restore the > entire pool from backup. > see: http://illumos.org/msg/ZFS-8000-8A > scan: resilvered 328M in 0h0m with 0 errors on Tue Nov 8 16:24:50 201= 6 > config: > > NAME STATE READ WRITE CKSUM > zpool DEGRADED 0 0 0 > raidz1-0 DEGRADED 0 0 0 > spare-0 DEGRADED 0 0 0 > 16161479624068136764 REMOVED 0 0 0 was /dev/da1 > da4 ONLINE 0 0 0 > 7947336420112974466 REMOVED 0 0 0 was /dev/da2 > da3 ONLINE 0 0 0 > spares > 16893112194374399469 INUSE was /dev/da4 > > errors: 2 data errors, use '-v' for a list > > pool: zroot > state: ONLINE > scan: none requested > config: > > NAME STATE READ WRITE CKSUM > zroot ONLINE 0 0 0 > da0p3 ONLINE 0 0 0 > > errors: No known data errors > > Anyway it is said :"One or more devices has experienced an error > resulting in data corruption." > but a cd to a filesystem of the pool doesn't crashed anymore. > > So the questions: > - why we have to issue a zpool clear in order to recover a "working" pool= ? > > - is it normal to have possible data corruption (as said in the > message), what it means exactly ? > As we understood normaly the pool should recover enough redondancy > informations to have a fonctional one, > and without possible data corruption, no ? > > Thank for you help, > Best regards > Jean-Marc & Roland > > > -- > LACROIX Jean-Marc office: W612 > Administrateur Syst=C3=A8mes et R=C3=A9seaux LJAD > phone: 04.92.07.62.51 fax: 04.93.51.79.74 > email: jml@unice.fr > Address: Laboratoire J.A.Dieudonne - UMR CNRS 7351 > Universite de Nice Sophia-Antipolis > Parc Valrose - 06108 Nice Cedex 2 - France > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"