From owner-freebsd-fs@FreeBSD.ORG Tue Aug 19 20:17:35 2014 Return-Path: Delivered-To: freebsd-fs@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 A2CFD7CC for ; Tue, 19 Aug 2014 20:17:35 +0000 (UTC) Received: from smtp.digiware.nl (unknown [IPv6:2001:4cb8:90:ffff::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 61D773B07 for ; Tue, 19 Aug 2014 20:17:35 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 8BF541534ED; Tue, 19 Aug 2014 22:17:31 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z4ThPWzmuDII; Tue, 19 Aug 2014 22:16:59 +0200 (CEST) Received: from [192.168.10.9] (vaio [192.168.10.9]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 641911534C4; Tue, 19 Aug 2014 22:16:59 +0200 (CEST) Message-ID: <53F3B0BD.406@digiware.nl> Date: Tue, 19 Aug 2014 22:17:01 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Ronald Klop , freebsd-fs@freebsd.org Subject: Re: Strange effect of zfs rename References: <53E61706.4010604@digiware.nl> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2014 20:17:35 -0000 On 18-8-2014 17:17, Ronald Klop wrote: > On Sat, 09 Aug 2014 14:41:42 +0200, Willem Jan Withagen > wrote: > >> Hoi, >> >> In the process of creating backups I have this sequence of: >> >> /sbin/zfs destroy zfsraid/backups@Saturday-2 >> /sbin/zfs rename -f zfsraid/backups@Saturday zfsraid/backups@Saturday-2 >> /sbin/zfs snapshot zfsraid/backups@Saturday >> >> But then I end up with: >> # cd /backups/.zfs/snapshot >> # ll >> ls: Saturday-2: Device busy >> total 116 >> 0 dr-xr-xr-x 11 root wheel 11 Aug 9 14:15 ./ >> 0 dr-xr-xr-x 4 root wheel 4 Jul 30 22:07 ../ >> 17 drwxr-xr-x 13 root wheel 16 Jul 31 09:54 20140801/ >> 17 drwxr-xr-x 18 root wheel 21 Aug 5 01:03 Friday/ >> 17 drwxr-xr-x 16 root wheel 19 Aug 3 01:03 Monday/ >> 17 drwxr-xr-x 15 root wheel 18 Aug 2 01:03 Sunday/ >> 17 drwxr-xr-x 18 root wheel 21 Aug 5 01:03 Thursday/ >> 17 drwxr-xr-x 17 root wheel 20 Aug 4 01:03 Tuesday/ >> 17 drwxr-xr-x 18 root wheel 21 Aug 5 01:03 Wednesday/ >> Exit 1 >> >> And the device does not becomen not-busy even after a "long" wait. >> >> The way to remedy this is: >> /sbin/zfs unmount -f zfsraid/backups >> /sbin/zfs mount zfsraid/backups >> >> After that the snapshot-dir is as it should. >> >> I'm running: >> FreeBSD zfs.digiware.nl 9.3-STABLE FreeBSD 9.3-STABLE #272 r269145M: Sun >> Jul 27 06:50:06 CEST 2014 >> root@zfs.digiware.nl:/usr/obj/usr/srcs/src9/src/sys/ZFS amd64 >> >> Can other reproduce this? Or is my system suffering from bitrot? >> >> Regards, >> --WjW > > I don't see this. I used to work on 9-STABLE and now on 10-STABLE (from > august 5th). > > I use zfs rename a lot for handling my snapshots, but I do not use the > -f option. I must say I never need to go into the .zfs/snapshot > directories, so they are mounted seldom. I just went into them today for > a test, but I don't have 'Device busy' problems. Do you keep such a > directory active somewhere? No not really, it is like you suggest: rarely go into the snapshots for recovery. But I do keep 'm online. I'm just using test(1) to see if the snapshot I'd like to destroy is really there. Which is easily done by testing if the snapshot dir exists. --WjW