From owner-freebsd-stable@FreeBSD.ORG Wed Jun 4 15:41:51 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F448106566B for ; Wed, 4 Jun 2008 15:41:51 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 868E18FC1D for ; Wed, 4 Jun 2008 15:41:51 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 2546C1CC031; Wed, 4 Jun 2008 08:41:51 -0700 (PDT) Date: Wed, 4 Jun 2008 08:41:51 -0700 From: Jeremy Chadwick To: Andriy Gapon Message-ID: <20080604154151.GA29932@eos.sc1.parodius.com> References: <4846AFC3.3050101@icyb.net.ua> <20080604152332.GE63348@deviant.kiev.zoral.com.ua> <4846B5D9.1050903@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4846B5D9.1050903@icyb.net.ua> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Kostik Belousov , freebsd-stable@freebsd.org Subject: Re: mystery: lock up after fs dump X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2008 15:41:51 -0000 On Wed, Jun 04, 2008 at 06:33:45PM +0300, Andriy Gapon wrote: > on 04/06/2008 18:23 Kostik Belousov said the following: > > On Wed, Jun 04, 2008 at 06:07:47PM +0300, Andriy Gapon wrote: > [snip] > >> dumps are done on live filesystems using -L. > [snip] > >> 4. both systems have gjournal support (on 6.X it is added via a > >> "non-official" patch), there are gjournaled filesystems on both systems > >> and they are dumped. > > > > Do you use snapshots on the gjournaled fs ? I believe this is problematic. > > Yes, I do via dump -L. I don't otherwise (no mksnap_ffs). > I had some thoughts about that. > But... I remember discussing this on geom list and I think pjd said that > this should work and also it worked for me flawlessly except for that > one moment. > BTW, those filesystems are mounted like the following: > ufs, asynchronous, local, noatime, gjournal > This is to say that I do not mix gjournal and softupdates, which is also > possible (at least not prohibited). I haven't seen hard system lock-ups when using dump (the -L on UFS2 systems is implied, but you're not using softupdates, so maybe it's not implied on such), but I have seen all I/O on the system lock up hard until the actual snapshot finishes being taken. I mentioned this a while ago on -stable (not sure; I can dig up the thread), and was told that essentially this is a known problem with snapshots on UFS2, and that the problem over time gets worse and worse. Ultimately I stopped using dump and switched to rsync. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |