From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 01:07:01 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 53036733 for ; Thu, 4 Dec 2014 01:07:01 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 C0B36ABC for ; Thu, 4 Dec 2014 01:07:00 +0000 (UTC) Received: from pluto.sol.local ([188.103.87.225]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0Lt1S6-1Y2Hw609iU-012b6r; Thu, 04 Dec 2014 02:06:52 +0100 Message-ID: <547FB3AB.6030003@gmx.net> Date: Thu, 04 Dec 2014 02:06:51 +0100 From: Michael Schmiedgen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.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> In-Reply-To: <547FAF3C.5080002@multiplay.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:S8xuczgi/uijVSwa1Ay2k4ES1/2nR3QdqGXmbR2xmnpxfGhjvg2 XaK6mZ0D209iU60fX1fsXUk+TRmBI5B7jjubqGQ/xXkkE07AsRdxhoTQVk9NmWRYOzaJLEn eaNPE3xS6JpP+Hif2sR+H2oXBL9/h+tO0Q+au5ZVopPx5XPIs3WnNamQZmQ+YgOp07L6ODj 4cTW5xBit9JziG1BwnzbQ== 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 01:07:01 -0000 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. Ok, will try this. > Also ensure your loading zfs in /etc/rc.conf > zfs_enable="YES" It was there. > Check you don't have anything zfs custom in /boot/loader.conf > > You should just have the two zfs related lines such as: > zfs_load="YES" > vfs.root.mountfrom="zfs:tank/root" It was there. I commented all others out. > Your pool layout does look a little odd from your zpool get all as > bootfs seems to be set to just "tank" is that correct as its quite none > standard? If not and your root is tank/root then that might also be your > issue. It is tank. Back in 2012 there was no installer with ZFS features, it was done manually, with gnop trick and aligned partitions. Datasets are used for certain purposes, but kernel and userland resides on the root dataset 'tank'. > Next up there should be no need for mountpoint legacy / should do just > fine. > > If you do have a single partition install you might want to consider > switching to something more standard which looks something like: > NAME USED AVAIL REFER MOUNTPOINT > tank 853G 292G 46.5K none > tank/root 21.6G 292G 21.3G / > tank/root/tmp 11.2M 292G 11.2M /tmp > tank/root/var 270M 292G 270M /var > > Oh and ensure your boot loader has been updated: > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada1 I have already done this, at least the gpt zfs bootcode. So I will give the cache file a try when I am at work tomorrow and report back. Thank you, much appreciated! Michael