From owner-freebsd-fs@FreeBSD.ORG Wed Apr 26 21:07:50 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 99A9916A40B for ; Wed, 26 Apr 2006 21:07:50 +0000 (UTC) (envelope-from robert@mhi-tx.com) Received: from mail.mhi-tx.com (mail.mhi-tx.com [207.71.0.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BD8B43D97 for ; Wed, 26 Apr 2006 21:07:34 +0000 (GMT) (envelope-from robert@mhi-tx.com) Received: from localhost ([127.0.0.1]) by mail.mhi-tx.com (Kerio MailServer 5.7.10) (using TLSv1/SSLv3 with cipher AES256-SHA (256 bits)) for freebsd-fs@freebsd.org; Wed, 26 Apr 2006 16:01:56 -0500 Message-ID: <444FE114.7010106@mhi-tx.com> Date: Wed, 26 Apr 2006 16:07:32 -0500 From: Robert User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: 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: Wed, 26 Apr 2006 21:07:50 -0000 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)? Falconstor does not "support" FreeBSD but I am trying to make it work. I am guessing that if the fs can be put into a state as in "During steps three through six, all write activity on the filesystem is suspended." (http://www.usenix.org/publications/library/proceedings/bsdcon02/mckusick/mckusick_html/index.html) then an external snapshot could be taken of the system using IPStor or any other SAN software? Perhaps a tool that uses vn_start_write() and vn_write_finished() that a sysadmin could use without mucking things up. Am I reading too much into this, should I not worry about the filesystem state and simply allow background fsck to run when booting from any of the inconsistent snapshots? TIA Robert