From owner-freebsd-fs@FreeBSD.ORG Sun Sep 15 13:36:15 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8266FD3C for ; Sun, 15 Sep 2013 13:36:15 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 33A5321F4 for ; Sun, 15 Sep 2013 13:36:15 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r8FDa742044901; Sun, 15 Sep 2013 07:36:07 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r8FDa7WN044898; Sun, 15 Sep 2013 07:36:07 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 15 Sep 2013 07:36:07 -0600 (MDT) From: Warren Block To: Ronald Klop Subject: Re: Mounting from zfs failed with error 22 with gmirror In-Reply-To: Message-ID: References: <5234BE9E.1030308@FreeBSD.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 15 Sep 2013 07:36:07 -0600 (MDT) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Sep 2013 13:36:15 -0000 On Sun, 15 Sep 2013, Ronald Klop wrote: > Is it possible you used these disks with gmirror in the past and you did not > correctly clean the meta-data from the disks when you started using zfs? > So gmirror now detects meta-data, starts handling the disks in some way and > zfs does not get all the sectors of the disk it is expecting? Both the gmirrored swap and the ZFS mirror are using individual partitions, so a metadata conflict is less likely than with entire disks. Error 22 is EINVAL. Maybe GEOM is hiding label or partition names because of the gmirror mount, then ZFS can't find the members of the zmirror. Booting from a liveCD, loading ZFS and gmirror, then looking at partition names and labels might show what is missing. There is a version of mfsBSD (http://mfsbsd.vx.sk/) with ZFS.