From owner-freebsd-current@FreeBSD.ORG Tue Nov 26 20:07:22 2013 Return-Path: Delivered-To: freebsd-current@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 ESMTPS id 8CBAC1EF for ; Tue, 26 Nov 2013 20:07:22 +0000 (UTC) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7149A2940 for ; Tue, 26 Nov 2013 20:07:22 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1VlOuh-0007dO-Aa for freebsd-current@freebsd.org; Tue, 26 Nov 2013 12:07:15 -0800 Date: Tue, 26 Nov 2013 12:07:14 -0800 (PST) From: Beeblebrox To: freebsd-current@freebsd.org Message-ID: <1385496434634-5864187.post@n5.nabble.com> Subject: ZFS: sharenfs and "zdb no such file" errors MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Nov 2013 20:07:22 -0000 I had a previously discussed zpool related error on my susytem: (http://freebsd.1045724.n5.nabble.com/zpool-requires-re-import-on-reboot-td5861930.html#a5862468). This may be related. Now a different but equally odd error: On one of the pools with the import problem (poolname=da), I had: zfs set sharenfs="-network=192.168.2.0/24" da/data/amd64 When I start nfsd + mountd, TTY0 shows this error: bad exports list line: /mnt/data/amd64 bad exports list line: /mnt/amd64 I can only assume that I had the da zpool mounted as altroot=/mnt at some point in its history. After I zfs set sharenfs=off da/data/amd64 for debugging, the error persisted for some time then was gone when I first tried; now it persists even after a pool scrub. ZDB shows nothing odd with the "-Cl /dev/ada1p2" flag, but, zdb -d da/data/amd64 zdb: can't open 'da/data/amd64': No such file or directory I have same error for all pool-type commands. "# zdb -C da" for example. Regards ----- FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/ZFS-sharenfs-and-zdb-no-such-file-errors-tp5864187.html Sent from the freebsd-current mailing list archive at Nabble.com.