Date: Sun, 15 Sep 2013 07:36:07 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Ronald Klop <ronald-freebsd8@klop.yi.org> Cc: freebsd-fs@freebsd.org Subject: Re: Mounting from zfs failed with error 22 with gmirror Message-ID: <alpine.BSF.2.00.1309150715190.44798@wonkity.com> In-Reply-To: <op.w3f7ciiq8527sy@212-182-167-131.ip.telfort.nl> References: <5234BE9E.1030308@FreeBSD.org> <op.w3f7ciiq8527sy@212-182-167-131.ip.telfort.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1309150715190.44798>