From owner-freebsd-fs@FreeBSD.ORG Wed Aug 18 18:44:49 2010 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A325910656A8 for ; Wed, 18 Aug 2010 18:44:49 +0000 (UTC) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: from bewilderbeast.blackhelicopters.org (bewilderbeast.blackhelicopters.org [198.22.63.8]) by mx1.freebsd.org (Postfix) with ESMTP id 6330C8FC1B for ; Wed, 18 Aug 2010 18:44:48 +0000 (UTC) Received: from bewilderbeast.blackhelicopters.org (localhost [127.0.0.1]) by bewilderbeast.blackhelicopters.org (8.14.4/8.14.4) with ESMTP id o7IIX0Q9098991 for ; Wed, 18 Aug 2010 14:33:01 -0400 (EDT) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: (from mwlucas@localhost) by bewilderbeast.blackhelicopters.org (8.14.4/8.14.4/Submit) id o7IIX08e098989 for fs@freebsd.org; Wed, 18 Aug 2010 14:33:00 -0400 (EDT) (envelope-from mwlucas) Date: Wed, 18 Aug 2010 14:33:00 -0400 From: "Michael W. Lucas" To: fs@freebsd.org Message-ID: <20100818183300.GA98970@bewilderbeast.blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.5 (bewilderbeast.blackhelicopters.org [127.0.0.1]); Wed, 18 Aug 2010 14:33:01 -0400 (EDT) Cc: Subject: HAST secondary identifying when it's dirty? 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, 18 Aug 2010 18:44:49 -0000 Hi, I have a HAST device set up between two systems. It appears that the secondary doesn't know when it's dirty. Is there any way for the secondary to know that its copy is incomplete? For example, I had to resync my HAST partition due to a firewall issue. While the master knows the secondary is dirty, the secondary thinks it's complete. For example: master# hastctl status mirror: role: primary provname: mirror localpath: /dev/da0s2 extentsize: 2097152 keepdirty: 64 remoteaddr: 192.168.0.1 replication: memsync status: complete dirty: 24385683456 bytes secondary# hastctl status mirror: role: secondary provname: mirror localpath: /dev/da0s2 extentsize: 2097152 keepdirty: 0 remoteaddr: 192.168.0.2 replication: memsync status: complete dirty: 0 bytes The secondary doesn't realize it's 24GB out of sync. Is there any way for the secondary to get this information? Thanks, ==ml -- Michael W. Lucas mwlucas@BlackHelicopters.org http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ New book available: Network Flow Analysis http://www.networkflowanalysis.com/