From owner-freebsd-fs@FreeBSD.ORG Thu Apr 27 14:17:41 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F54716A400 for ; Thu, 27 Apr 2006 14:17:41 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 049DB43D4C for ; Thu, 27 Apr 2006 14:17:40 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k3REHe9m032247; Thu, 27 Apr 2006 09:17:40 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4450D278.5000802@centtech.com> Date: Thu, 27 Apr 2006 09:17:28 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Robert References: <444FE114.7010106@mhi-tx.com> <20060426211059.GA85780@xor.obsecurity.org> <4450B3B1.8070704@centtech.com> <4450D18D.9060101@mhi-tx.com> In-Reply-To: <4450D18D.9060101@mhi-tx.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1426/Wed Apr 26 13:03:01 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-fs@freebsd.org Subject: Re: suspend writes for external snapshot 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: Thu, 27 Apr 2006 14:17:41 -0000 Robert wrote: > Eric Anderson wrote: >> Kris Kennaway wrote: >> >>> On Wed, Apr 26, 2006 at 04:07:32PM -0500, Robert wrote: >>> >>>> Greetings, >>>> I am trying to determine if there is a way to suspend write activity >>>> on a FreeBSD filesystem (currently 6.0R) in order to take a snapshot >>>> with external SAN software (Falconstor IPStor)? >>> >>> >>> Use a FreeBSD snapshot and then image that? >> >> >> He can't do it that way because the Falconstor is a raw block device >> and has no idea the difference between a snapshot and other filesystem >> bits. >> >> >> Robert - we have some very alpha patches in house that allow >> suspension of UFS filesystems for things like this (also working on >> online UFS growing). I'm not sure how close we really are to letting >> it loose in the wild, but we will definitely be making all the patches >> available to whomever wants it. >> >> >> Eric >> >> >> > > Sounds great thank you, I will keep an eye out for the patches. > > I am still unclear as to the necessity of suspending writes based on the > following information from http://www.mckusick.com/softdep/ > > "By ensuring that the only inconsistencies are unclaimed blocks or > inodes, soft updates can eliminate the need to run a filesystem check > program after every system crash. Instead, the system is brought up > immediately. > > When it is convenient, a snapshot is taken and a background task can be > run on on that snapshot to reclaim any lost blocks and inodes. The use > of a snapshot allows normal filesystem activity to continue concurrently. " > > Does this mean that I can take a snapshot of an in use filesystem and > the only ill effects will be the lost blocks and inodes which can be > reclaimed with background fsck once the snapshot is booted? I believe so, yes. Someone correct me here if I am wrong. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------