Date: Tue, 10 Sep 2013 09:05:07 +0930 From: Shane Ambler <FreeBSD@ShaneWare.Biz> To: dweimer@dweimer.net Cc: freebsd-questions@freebsd.org Subject: Re: ZFS Snapshots Not able to be accessed under .zfs/snapshot/name Message-ID: <522E5B2B.7000705@ShaneWare.Biz> In-Reply-To: <a6c0402b555f4ce477fdc7ecfbd680b0@dweimer.net> References: <22a7343f4573d6faac5aec1d7c9a1135@dweimer.net> <520C405A.6000408@ShaneWare.Biz> <776e30b627bf30ece7545e28b2a2e064@dweimer.net> <23413f3a4b95328c0bc838e6ffad364d@dweimer.net> <a6c0402b555f4ce477fdc7ecfbd680b0@dweimer.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?522E5B2B.7000705>