From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 14:09:39 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 618009DE for ; Tue, 2 Dec 2014 14:09:39 +0000 (UTC) Received: from mail.nospam.fr.eu.org (saloon.dalton-brothers.org [IPv6:2001:bc8:3ac3::beef:1]) by mx1.freebsd.org (Postfix) with ESMTP id 2A400D85 for ; Tue, 2 Dec 2014 14:09:39 +0000 (UTC) Received: from mail.dupille.org (localhost [IPv6:::1]) by mail.nospam.fr.eu.org (Postfix) with ESMTP id 917031907 for ; Tue, 2 Dec 2014 15:09:30 +0100 (CET) Authentication-Results: mail.nospam.fr.eu.org; dkim=none reason="no signature"; dkim-adsp=fail (unprotected policy) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 02 Dec 2014 15:09:30 +0100 From: =?UTF-8?Q?St=C3=A9phane_Dupille?= To: freebsd-stable@freebsd.org Subject: Zpool is segfaulting Organization: Maison Message-ID: X-Sender: stephane@dupille.org User-Agent: Roundcube Webmail/1.0.3 X-Spam-Status: No, score=0.9 required=5.0 tests=AWL, BAYES_40, UNPARSEABLE_RELAY shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on spamd X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2014 14:09:39 -0000 Hello ! I've juste upgraded my server from 10.0-RELEASE to 10.1-RELEASE. Everything went well, exception in my daily periodic report, I've found that the command "zpool list" is behaving strangely : # zpool list bad property list: invalid property 'fragmentation' usage: list [-Hpv] [-o property[,...]] [-T d|u] [pool] ... [interval [count]] the following properties are supported: PROPERTY EDIT VALUES allocated NO capacity NO dedupratio NO <1.00x or higher if deduped> expandsize NO free NO freeing NO guid NO health NO size NO altroot YES autoexpand YES on | off autoreplace YES on | off bootfs YES cachefile YES | none comment YES dedupditto YES delegation YES on | off failmode YES wait | continue | panic listsnapshots YES on | off readonly YES on | off version YES feature@... YES disabled | enabled | active The feature@ properties must be appended with a feature name. See zpool-features(7). On a freshly installed 10.1-RELEASE it behaves correctly. But what is frightening me the most is that : # zpool upgrade This system supports ZFS pool feature flags. All pools are formatted using feature flags. Some supported features are not enabled on the following pools. Once a feature is enabled the pool may become incompatible with software that does not support the feature. See zpool-features(7) for details. POOL FEATURE --------------- zboot com.delphix:async_destroy zsh: segmentation fault (core dumped) zpool upgrade Again, it works perfeclty well on a freshly installed 10.1-RELEASE. So, on my server, I installed a mirror zfs on top of a GELI layer. I don't know if it's of any importance. I don't know where to look to fix this issue (if there's an issue, the system is behaving perfectly well). Best regards, SD