From owner-freebsd-hackers@FreeBSD.ORG Wed Oct 1 13:48:32 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A2249A48 for ; Wed, 1 Oct 2014 13:48:32 +0000 (UTC) Received: from eu1sys200aog113.obsmtp.com (eu1sys200aog113.obsmtp.com [207.126.144.135]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F275F8F8 for ; Wed, 1 Oct 2014 13:48:31 +0000 (UTC) Received: from mail-wi0-f172.google.com ([209.85.212.172]) (using TLSv1) by eu1sys200aob113.postini.com ([207.126.147.11]) with SMTP ID DSNKVCwGFL+8d+LKzl0cuTyRTDQqw+GpPyFT@postini.com; Wed, 01 Oct 2014 13:48:32 UTC Received: by mail-wi0-f172.google.com with SMTP id n3so618506wiv.11 for ; Wed, 01 Oct 2014 06:48:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:message-id:to:subject:cc:reply-to :in-reply-to; bh=GDaz6fv1JfHIyZ/Me8JYDxLcSB3R0DOIXHmANdG+f6Q=; b=FYu453AkOfZf6rz2kUZymBqAt3HAwyxOG1ut6h8V294X++a+CobY3SKAU1bJ1B21zC zruuaO4tc2YZqLRNwO3+jWrFSMsTcXjWrhBjEQU6EcHhjCvCaUnGnSLJUCN/SOMf87F/ 0CkD0mMsTpmbrmtpXe4aWeH5XrIMBbNLsqivU2xMZE2WWYMzBz2rQbJq5SLO6MpjpCkX nFbHBV+swSSiAJ00xGYFvkDfv6Grj5iNw1tw6PoeMUZ+I0FSQK/XGngsfw8bLLcHTUz/ Yu+f36tCZUSUG1bmmxrjWmAStFXYXVz+cMHzb81+6lwOo7VtOrQu5QkzvCCqyMAuYGKy kWQQ== X-Gm-Message-State: ALoCoQm6b4W0EtiteSSqRV8SehQC+5IVAfOKnHwB+5dwnz+46SNDmyY1E9JL4AQeuKndOZs6yImRGQzspNDtkLql+NtfYdVdG1WbtZ51N/9dgVcVgPniuXyXdYacNiQaaD4Kr6KOQmfvxCe6pu/su/237f7rk5fcCg== X-Received: by 10.194.204.232 with SMTP id lb8mr64768831wjc.0.1412171284067; Wed, 01 Oct 2014 06:48:04 -0700 (PDT) X-Received: by 10.194.204.232 with SMTP id lb8mr64768749wjc.0.1412171283531; Wed, 01 Oct 2014 06:48:03 -0700 (PDT) Received: from mech-as221.men.bris.ac.uk (mech-as221.men.bris.ac.uk. [137.222.187.221]) by mx.google.com with ESMTPSA id cz3sm1245432wjb.23.2014.10.01.06.48.02 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Oct 2014 06:48:02 -0700 (PDT) Received: from mech-as221.men.bris.ac.uk (localhost [127.0.0.1]) by mech-as221.men.bris.ac.uk (8.14.9/8.14.9) with ESMTP id s91Dm19V084972 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 1 Oct 2014 14:48:01 +0100 (BST) (envelope-from mexas@mech-as221.men.bris.ac.uk) Received: (from mexas@localhost) by mech-as221.men.bris.ac.uk (8.14.9/8.14.9/Submit) id s91Dm1n3084971; Wed, 1 Oct 2014 14:48:01 +0100 (BST) (envelope-from mexas) Date: Wed, 1 Oct 2014 14:48:01 +0100 (BST) From: Anton Shterenlikht Message-Id: <201410011348.s91Dm1n3084971@mech-as221.men.bris.ac.uk> To: jkh@mail.turbofuzz.com, kraduk@gmail.com Subject: Re: cluster FS? Reply-To: mexas@bristol.ac.uk In-Reply-To: Cc: freebsd-hackers@freebsd.org, mexas@bristol.ac.uk X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Oct 2014 13:48:32 -0000 >From jkh@mail.turbofuzz.com Wed Oct 1 14:22:36 2014 > >> On Oct 1, 2014, at 2:03 PM, krad wrote: >> >> These are my definitions, hopefully it makes some stuff a little clearer > >Thanks for the exposition - if that doesn’t help Anton, I don’t know what will. :-) It did. Thanks a lot. >To answer Anton’s previous question, he just needs to read the PDF he cited a little more closely. HP has obviously provided some sort of concurrent access mode to their SAN, but it's only active/active if you have one of the supported operating systems. Presumably, HP also provides drivers for those OSes which provide some sort of interlock support, though again, it’s not clear just what sort of filesystems you can put on the SAN and still keep the active/active concurrency. It’s very tricky, and the penalty for getting it wrong is corrupted data, so I’d tend to put my money on an actual filesystem-level solution which provides concurrent access, like glusterfs. That just went BETA with FreeBSD support, so who knows, maybe it’s becoming a viable solution. I have zero experience with deploying glusterfs, however, so I cannot speak to that. > ok, I get it - my plans are way beyond my IT expertise (amateur). Thanks again Anton