From owner-freebsd-fs@FreeBSD.ORG Wed Jan 22 08:53:01 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 AFDF978A for ; Wed, 22 Jan 2014 08:53:01 +0000 (UTC) Received: from umail.aei.mpg.de (umail.aei.mpg.de [194.94.224.6]) by mx1.freebsd.org (Postfix) with ESMTP id 420CE1FF5 for ; Wed, 22 Jan 2014 08:53:00 +0000 (UTC) Received: from mailgate.aei.mpg.de (mailgate.aei.mpg.de [194.94.224.5]) by umail.aei.mpg.de (Postfix) with ESMTP id 0C5DF201004; Wed, 22 Jan 2014 09:52:59 +0100 (CET) Received: from mailgate.aei.mpg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id DA022405889; Wed, 22 Jan 2014 09:52:58 +0100 (CET) Received: from intranet.aei.uni-hannover.de (ahin1.aei.uni-hannover.de [130.75.117.40]) by mailgate.aei.mpg.de (Postfix) with ESMTP id 5DF32406AF1; Wed, 22 Jan 2014 09:52:58 +0100 (CET) Received: from cascade.aei.uni-hannover.de ([10.117.15.111]) by intranet.aei.uni-hannover.de (Lotus Domino Release 8.5.3FP6) with ESMTP id 2014012209524798-1390 ; Wed, 22 Jan 2014 09:52:47 +0100 Date: Wed, 22 Jan 2014 09:52:46 +0100 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: Matt Magoffin Subject: Re: ZFS snapshot renames failing after upgrade to 9.2 Message-Id: <20140122095246.65ea2196.gerrit.kuehn@aei.mpg.de> In-Reply-To: References: <0C9FD4E1-0549-4849-BFC5-D8C5D4A34D64@msqr.us> <54D3B3C002184A52BEC9B1543854B87F@multiplay.co.uk> <333D57C6A4544067880D9CFC04F02312@multiplay.co.uk> <26053_1387447492_52B2C4C4_26053_331_1_20131219105503.3a8d1df3.gerrit.kuehn@aei.mpg.de> <20131219165549.9f2ca709.gerrit.kuehn@aei.mpg.de> <20131219174054.91ac617a.gerrit.kuehn@aei.mpg.de> <20131220100522.382a39ac.gerrit.kuehn@aei.mpg.de> Organization: Max Planck Gesellschaft X-Mailer: Sylpheed 3.1.3 (GTK+ 2.24.19; amd64-portbld-freebsd8.2) Mime-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on intranet/aei-hannover(Release 8.5.3FP6|November 21, 2013) at 01/22/2014 09:52:48, Serialize by Router on intranet/aei-hannover(Release 8.5.3FP6|November 21, 2013) at 01/22/2014 09:52:58, Serialize complete at 01/22/2014 09:52:58 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-PMX-Version: 6.0.2.2308539, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.1.22.83915 X-PerlMx-Spam: Gauge=IIIIIIIII, Probability=9%, Report=' MULTIPLE_RCPTS 0.1, HTML_00_01 0.05, HTML_00_10 0.05, MIME_LOWER_CASE 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1300_1399 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_FROM 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MULTIPLE_RCPTS_CC_X2 0, __SANE_MSGID 0, __SUBJ_ALPHA_NEGATE 0, __TO_MALFORMED_2 0, __URI_NO_PATH 0, __URI_NO_WWW 0, __URI_NS ' Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jan 2014 08:53:01 -0000 On Wed, 22 Jan 2014 14:37:32 +1300 Matt Magoffin wrote about Re: ZFS snapshot renames failing after upgrade to 9.2: MM> I missed the continuation of this thread, but wanted to add in that MM> this still happens for me (snapshot renames lead to unusable MM> snapshots). Well, I guess there was no continuation so far. On the 9.2-system under question, I changed the backup/snapshot scheme to use the dates in the names instead of doing logrotate stuff (using sysutils/zfs-periodic instead of sysutils/freebsd-snapshot) to circumvent the issue. MM> I recently updated to 9.2-p3, and after restarting the system my MM> scripts were able to rename the existing snapshots as expected, but MM> only one time. When my backup script attempted to rename the new MM> snapshot and the older ones during its second run since the restart, MM> it failed and ended up in the unusable state. I have the feeling that the issue depends on wether the snapshot was used before, is still mounted or something like that. I think when I had just the snapshots running (without the backup jobs), I did not see this (but I may be wrong with this). MM> As for 9.1, I never had this problem in 9.1. It only started happening MM> for me after updating to 9.2. Indeed, in 9.1 this was fine. Maybe we should file a proper bug report for this? cu Gerrit