From owner-freebsd-fs@FreeBSD.ORG Tue Dec 7 11:15:57 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E373C1065675 for ; Tue, 7 Dec 2010 11:15:57 +0000 (UTC) (envelope-from a.smith@ukgrid.net) Received: from mx0.ukgrid.net (mx0.ukgrid.net [89.21.28.41]) by mx1.freebsd.org (Postfix) with ESMTP id A0DAC8FC1A for ; Tue, 7 Dec 2010 11:15:57 +0000 (UTC) Received: from [89.21.28.38] (port=65209 helo=omicron.ukgrid.net) by mx0.ukgrid.net with esmtp (Exim 4.72; FreeBSD) envelope-from a.smith@ukgrid.net envelope-to freebsd-fs@freebsd.org id 1PPvWV-000GP4-FK; Tue, 07 Dec 2010 11:15:55 +0000 Received: from cpc2-mort2-0-0-cust506.croy.cable.virginmedia.com (cpc2-mort2-0-0-cust506.croy.cable.virginmedia.com [82.43.121.251]) by webmail2.ukgrid.net (Horde Framework) with HTTP; Tue, 07 Dec 2010 11:15:55 +0000 Message-ID: <20101207111555.17494gq2v9f0sias@webmail2.ukgrid.net> Date: Tue, 07 Dec 2010 11:15:55 +0000 From: a.smith@ukgrid.net To: freebsd-fs@freebsd.org References: <20101202114522.16601wx7crv5zhz4@webmail2.ukgrid.net> In-Reply-To: <20101202114522.16601wx7crv5zhz4@webmail2.ukgrid.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.9) / FreeBSD-8.1 Subject: Re: spurious ZFS "dataset does not exist" errors X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2010 11:16:02 -0000 Hi, I have now repeated this several times and continue to receive these weird errors. To confirm my steps to produce this, I am simply doing: zpool create nas1bkp raidz ada4p1 ada5p1 ada6p1 ada7p1 zfs send nas1/iscsi-cctv@another | zfs receive nas1bkp/iscsi-cctv The send takes over 12 hours as the volume size is nearly 3TB. I therefore used the disown command to allow the process to complete while not connected to the server. I tested this also using the nohup command with the same result. I also tested using a small test volume of just 100M and I don't get the same errors. So its only occuring with very large send/receive operations. If no one has any ideas, or any other tests I might do then I guess I'm just gona have to ignore these as the pool seems fine aparte from these... :S thanks Andy. Quoting a.smith@ukgrid.net: > Hi, > > I have been setting up a new ZFS pool to which I am replicate via > ZFS send/receive a (raw) volume from another pool. After creating > the duplicate volume in the new pool and having tested that it works > (it does) I exported the ZFS pool and it gives me the following > errors: > > # zpool export nas1bkp > cannot open 'nas1bkp/iscsi-cctvp3': dataset does not exist > cannot open 'nas1bkp/iscsi-cctvp2': dataset does not exist > cannot open 'nas1bkp/iscsi-cctvp1': dataset does not exist > > Its quite right, those datasets don't exist. But why is it even > trying to touch something that doesn't and has never existed. > Devices that actually exist are shown here: > > # zfs list > NAME USED AVAIL REFER MOUNTPOINT > nas1 3.19T 2.15T 648M /nas1 > nas1/cctv 2.53M 2.15T 2.53M /nas1/cctv > nas1/iscsi-cctv 3.19T 2.65T 2.65T - > nas1/zfssend 28.4K 50.0G 28.4K /nas1/zfssend > nas1bkp 3.19T 2.15T 28.4K /nas1bkp > nas1bkp/iscsi-cctv 3.19T 2.65T 2.65T - > nas1bkp/zfsrecv 26.9K 50.0G 26.9K /nas1bkp/zfsrecv > > > Anyone any idea whats going on? Spurious errors make me nervous! > > thanks Andy. > > > >