From owner-freebsd-questions@FreeBSD.ORG Mon Sep 9 23:35:11 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8C7A9678 for ; Mon, 9 Sep 2013 23:35:11 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail06.adl2.internode.on.net (ipmail06.adl2.internode.on.net [IPv6:2001:44b8:8060:ff02:300:1:2:6]) by mx1.freebsd.org (Postfix) with ESMTP id 248F12BBA for ; Mon, 9 Sep 2013 23:35:10 +0000 (UTC) Received: from ppp118-210-73-223.lns20.adl2.internode.on.net (HELO leader.local) ([118.210.73.223]) by ipmail06.adl2.internode.on.net with ESMTP; 10 Sep 2013 09:05:10 +0930 Message-ID: <522E5B2B.7000705@ShaneWare.Biz> Date: Tue, 10 Sep 2013 09:05:07 +0930 From: Shane Ambler User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130516 Thunderbird/17.0.6 MIME-Version: 1.0 To: dweimer@dweimer.net Subject: Re: ZFS Snapshots Not able to be accessed under .zfs/snapshot/name References: <22a7343f4573d6faac5aec1d7c9a1135@dweimer.net> <520C405A.6000408@ShaneWare.Biz> <776e30b627bf30ece7545e28b2a2e064@dweimer.net> <23413f3a4b95328c0bc838e6ffad364d@dweimer.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Sep 2013 23:35:11 -0000 On 09/09/2013 22:38, dweimer wrote: > A quick update on this, in case anyone else runs into it, I did > finally try on the 2nd of this month to delete my UFS volume, and > create a new ZFS volume to replace it. I recreated the Squid cache > directories and let squid start over building up cache. So far their > hasn't been a noticeable impact on performance with the switch over, > and the snapshot problem has not reoccurred since making the change. > Its only a week into running this way but the problem before started > within 36-48 hours. > From what you mentioned earlier you appear to use dates in your snapshot names. So kern/161968 - shouldn't affect you. For others using zfs volumes - check kern/161968 : [zfs] [hang] renaming snapshot with -r including a zvol snapshot causes total ZFS freeze/lockup