From owner-freebsd-fs@FreeBSD.ORG Tue Oct 29 13:17:31 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 204E6DAB for ; Tue, 29 Oct 2013 13:17:31 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-ee0-x22b.google.com (mail-ee0-x22b.google.com [IPv6:2a00:1450:4013:c00::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AE0CB265D for ; Tue, 29 Oct 2013 13:17:30 +0000 (UTC) Received: by mail-ee0-f43.google.com with SMTP id b47so2663377eek.16 for ; Tue, 29 Oct 2013 06:17:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=N40p25gECZewuhmwVYjxbWLrPsiIEBxrZ/Fj01KLbEw=; b=ARHPSJmivBwNa51LF0pByWUKjtCd991OJJzRWIyYWMmgkuDlHu+50k7PmER1ykOEmt YODiv2mLHVZU1hbgbKGoWpHP97qmikb5IDoKeB8xIY9I47vQ0rxKRStvQZA/5hbYlyKQ aE1cLyfvdi+n6iBuu5Q82m12ZGGbk8SwFrsf5AcJwg2W2C3PkvyqsDYumkdCiK6vBgxN kwbIIilcuoZ8KW53zTZXPJuutzzawyYZE/TtQhCjq1W6B0WLNLy9yxQlLuwb6u6C+roa je+y9G+2dBnh4J354RhARJ+MbI6vx6LOo9rMpbdbwFEKz7sHcV4Gqfd8v/UsVis8LF3T i94w== X-Received: by 10.14.6.73 with SMTP id 49mr1721014eem.117.1383052649101; Tue, 29 Oct 2013 06:17:29 -0700 (PDT) Received: from localhost ([188.230.122.226]) by mx.google.com with ESMTPSA id bn13sm70262466eeb.11.2013.10.29.06.17.27 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 29 Oct 2013 06:17:28 -0700 (PDT) Date: Tue, 29 Oct 2013 15:17:26 +0200 From: Mikolaj Golub To: freebsd-fs@freebsd.org Subject: Re: HAST - Unable to receive request header: Socket is not connected (10.0-BETA1) Message-ID: <20131029131612.GA43106@gmail.com> References: <20131029072708.GC86932@margz.perth.internal> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131029072708.GC86932@margz.perth.internal> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2013 13:17:31 -0000 On Tue, Oct 29, 2013 at 06:27:08PM +1100, Wilkinson, Alex wrote: > [DEBUG][2] Checking hooks. > [DEBUG][2] [export] (primary) remote_send: Taking request. > [DEBUG][2] [export] (primary) remote_guard: Checking connections. > [DEBUG][2] Checking hooks. > [DEBUG][2] [export] (primary) remote_guard: Reconnecting to tcp4://172.18.3.12. > [DEBUG][1] [export] (primary) Negotiated protocol version 2. > [WARNING] [export] (primary) Data size differs between nodes (local=128819612160, remote=128848941568). It looks like you created resources of different size on differen nodes. If the primary detects media size mismatch it closes the connection. Does mfid0p4 size differs on host-a and host-b? If it does use -m option in `hastctl create' to specify the same size on both nodes. You can run `hastctl dump' (on both nodes) to see what HAST currently thinks about media size. > [ERROR] [export] (secondary) Unable to receive request header: Socket is not connected. This is a consequence of the primary closing the connection after detecting media size mismatch. -- Mikolaj Golub