From owner-freebsd-fs@FreeBSD.ORG Wed Jun 20 19:36:37 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9D28516A41F for ; Wed, 20 Jun 2007 19:36:37 +0000 (UTC) (envelope-from SRS0=5IyI=LU=ira.uka.de=esk@srs.kundenserver.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.174]) by mx1.freebsd.org (Postfix) with ESMTP id 317AE13C448 for ; Wed, 20 Jun 2007 19:36:36 +0000 (UTC) (envelope-from SRS0=5IyI=LU=ira.uka.de=esk@srs.kundenserver.de) Received: from [213.144.1.98] (helo=localhost) by mrelayeu.kundenserver.de (node=mrelayeu8) with ESMTP (Nemesis), id 0ML31I-1I15yB3hKr-00045m; Wed, 20 Jun 2007 21:36:34 +0200 From: Espen Skoglund MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18041.33127.677804.653910@gargle.gargle.HOWL> Date: Wed, 20 Jun 2007 21:35:03 +0200 To: Kostik Belousov In-Reply-To: <20070620165746.GX2268@deviant.kiev.zoral.com.ua> References: <18041.21810.297355.202403@gargle.gargle.HOWL> <20070620165746.GX2268@deviant.kiev.zoral.com.ua> X-Mailer: VM 7.17 under 21.4 (patch 20) "Double Solitaire" XEmacs Lucid X-Provags-ID: V01U2FsdGVkX18ZXf4HfkAEDfFO2Mm1nVzer/m701slsnbeMdR yhhgbUs/CGWcnvAsdrKnR89PKiOZgs2izkNZrRLnqlnArO1S/r DrEZiquQ5megPa/yQBErQ== Cc: freebsd-fs@freebsd.org, Espen Skoglund Subject: Re: Snapshot usage guidelines (to avoid stability issues) 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: Wed, 20 Jun 2007 19:36:37 -0000 [Kostik Belousov] >> Looking at PRs and mailing lists there seems to be mainly two >> outstanding stability issues with snapshots: a) snapshotted fs >> running full, and b) deleting large amount of files on an fs with >> multiple snapshots. The former issue, while certainly annoying, >> one could be able to work around. The latter issue, on the other >> hand, seems more like a definite show stopper. >> >> Am I right in inferring that the two above cases are main issues >> with snaphots at this time, or are there other known gotchas that I >> have to look out for. > About the issue b). Are you system sources before or after > 2007-06-11 10:53:48 UTC ? Or simply show me the version of > sys/ufs/ffs/ffs_snapshot.c. > If it is less then 1.103.2.24, see developers handbook for > instruction on reporting deadlocks. Ok. Thanks. Looking at the CVS logs after the hangup I wasn't sure whether the last commits addressed any of my problems. My kernel was from June 9, so I just missed the update you refer to. Unfortunately I didn't have any debug options turned on in my kernel. Also, I wasn't able to log into the system in any way so there was not much information I could gather. Will try the update once I find a suitable time that doesn't mess up my/our work schedule. If the update does indeed solve problem (b) then I can actually make use of snapshots. Huzzah! eSk