From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 11:26:32 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 5DCC5562 for ; Thu, 4 Dec 2014 11:26:32 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E6DA1258 for ; Thu, 4 Dec 2014 11:26:31 +0000 (UTC) Received: from [192.168.10.5] ([62.246.110.10]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0LgYuT-1Xc3Mn3ZHZ-00o1WF; Thu, 04 Dec 2014 12:26:28 +0100 Message-ID: <548044E6.1020703@gmx.net> Date: Thu, 04 Dec 2014 12:26:30 +0100 From: Michael Schmiedgen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Steven Hartland , 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> In-Reply-To: <547FB3AB.6030003@gmx.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:9Lv+lHJGqq4UG8RihTD6L89YJ1ziix04yvho/wsGr1/fRjO1b8E v41fqlvgmBx1lrWzztHAbAG9T7mjRV2u47s24ESXXt8aR4ppPVEzQwqq1lLhkGh4JjOvG9S C8VZn0KJJWH+eaWwZTJcE6TaUHkvCGEs+C2cq0moxixr3cQhfcMKBaDGghI5YiVgJSX8y7/ Q4inUjZ+YCaOC75KrwmIA== X-UI-Out-Filterresults: notjunk:1; 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:26:32 -0000 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. Thanks, Michael