Date: Tue, 29 Oct 2013 15:17:26 +0200 From: Mikolaj Golub <to.my.trociny@gmail.com> 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> In-Reply-To: <20131029072708.GC86932@margz.perth.internal> References: <20131029072708.GC86932@margz.perth.internal>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131029131612.GA43106>