From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 11:50:23 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C207BB9C for ; Thu, 4 Dec 2014 11:50:23 +0000 (UTC) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 60A286C9 for ; Thu, 4 Dec 2014 11:50:23 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id h11so27591310wiw.3 for ; Thu, 04 Dec 2014 03:50:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=CQgqUSehAgJjppiPQ10Ffp4ci5CbTT/OwiyUUPz4BCU=; b=AK6Z3FTCbyJMuyPNYBOEwInKpkDvnXit+xqQzCQLcevJj/w0vmgy/HqDRpJMSjTBtZ ZXOV5JL1QwQhiXq9L1mERdbXa3scmKHmEHL3fTaujKYndhoDnx1jYkTFQUD38M8q5IGz MzpYObGz2HKq3HwUT024gee1+vPyZzQQyS38Iv5hJ8L+E0gHGfiT5ZLVW5xKtyfCMS7x 088LzPRz30Ll5ourjD4qzgwYqqZhx62PNRIBQ5PzYSVJEvRnNRiooQeF/Xqv/79gQQro 7eB/J2Kc66NGiJSoh1JDL69Ya7EMRv7byw+ZPAgzG8/P27mAwVk79uZH8+W1mvUtPFBJ qF3A== X-Gm-Message-State: ALoCoQmvVKWVf9XAlMZgcWUMlg823sRh1XCh3dxvI6HAgW8zQKSu1Dx87Qky2sTX9dU33zXs0XE0 X-Received: by 10.194.187.164 with SMTP id ft4mr15200076wjc.76.1417693821138; Thu, 04 Dec 2014 03:50:21 -0800 (PST) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by mx.google.com with ESMTPSA id j2sm40190201wjs.28.2014.12.04.03.50.20 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Dec 2014 03:50:20 -0800 (PST) Message-ID: <54804AF3.9020805@multiplay.co.uk> Date: Thu, 04 Dec 2014 11:52:19 +0000 From: Steven Hartland User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Michael Schmiedgen , freebsd-stable@freebsd.org Subject: Re: ZFS 'mount error 5' hits production server References: <547F6E54.5020706@takwa.de> <547F98AF.9070701@multiplay.co.uk> <547FA5A9.1010600@gmx.net> <547FAF3C.5080002@multiplay.co.uk> <547FB3AB.6030003@gmx.net> <548044E6.1020703@gmx.net> In-Reply-To: <548044E6.1020703@gmx.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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: Thu, 04 Dec 2014 11:50:23 -0000 On 04/12/2014 11:26, Michael Schmiedgen wrote: > On 04.12.2014 02:06, Michael Schmiedgen wrote: >> On 12/04/2014 01:47, Steven Hartland wrote: >>> Unfortunately error 5 isn't very helpful as that's just EIO :( >>> >>> When booted from the old kernel try moving out the cache file e.g. >>> mv /boot/zfs/zpool.cache /boot/zfs/zpool.cache.old >>> >>> If for some reason your cache file and your disks are out of sync that >>> might help. > > I created a new cache file. It is slightly larger in size. But > no luck either. I am running out of ideas. :( > > As I said I had a similar 'mount error 5' problem at home some weeks > ago with CURRENT and custom kernel: > https://lists.freebsd.org/pipermail/freebsd-current/2014-October/052900.html > > > Solution was there to not remove the virtual machine stuff on > bottom of the kernel config. Very strange. Also the commit r271963 > (callout convert) that first triggered the problem seems to be > unrelated. Strange. > > And some months ago I had a 'mount error 5' problem if loading > nvidia driver in loader.conf, also on my desktop machine at home. > > I found similar 'error 5' problems on the mailing list, but no solution > at all. > > One thing I can try is to 4K align the start of the boot partition, but > at the moment this is a bit risky, I have no physical access to the > machine. > > Please tell if I should provide some more information. Did you try converting from tank from legacy to standard mount point?