From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 30 12:27:02 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 491987E1 for ; Tue, 30 Sep 2014 12:27:02 +0000 (UTC) Received: from eu1sys200aog104.obsmtp.com (eu1sys200aog104.obsmtp.com [207.126.144.117]) (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 990B219F for ; Tue, 30 Sep 2014 12:27:00 +0000 (UTC) Received: from mail-we0-f177.google.com ([74.125.82.177]) (using TLSv1) by eu1sys200aob104.postini.com ([207.126.147.11]) with SMTP ID DSNKVCqhjVqti65x8Jti6vtMegtU9eqHEklH@postini.com; Tue, 30 Sep 2014 12:27:01 UTC Received: by mail-we0-f177.google.com with SMTP id k48so86720wev.36 for ; Tue, 30 Sep 2014 05:26:53 -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=QHVwLQcm8vaQtesTYRfUewrr+/GJ5jrqDq0OEJ6qZMM=; b=kS5kAzo0UV91FYnnn35yLVONN1hMoGJSA8mXb4REp+DU6+oVrIoz8PN35K8IN4bXiI 3vgxXAACP2ZI+7hUTMVDKWa8xgH2ejoaO4itRGgdF/DduY4GhJgeLGLXu77WD9JfrCUx AcCU6VLX/1FeF8Vsh++/uKOPKeFNnXPylCfqvpBBM+lhvPZBsoOWWkb4nyTalNUEYuVG q0bfLpTRsjsgqSg7/uF973QILNBxYqDjOwi0aqrtwUZ5zSwWtoFoImS/T7ew1dYiOI4z qhzl7dYeZcvh6DHVQZK12SWWaUK46KJAYE+OhS7xamye1nv4p7dratXlLpqKJdRGbTYn 83Cw== X-Received: by 10.180.76.100 with SMTP id j4mr5069383wiw.51.1412078276097; Tue, 30 Sep 2014 04:57:56 -0700 (PDT) X-Gm-Message-State: ALoCoQnn/j1SlF70/8wtiB1P30wHK7w074Ee7wgVu2oMjTBapgpsxccw0cXUdjvJj4Y7S7gxI/wQQ2fYUW3pUS+s/s71r4/9jUng9fWblgGypBYXy6BtbhagHON7GC4uZMjGwmyPmBmOS8yw68Jv/CPE3ult/86IOQ== X-Received: by 10.180.76.100 with SMTP id j4mr5069370wiw.51.1412078275989; Tue, 30 Sep 2014 04:57:55 -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 cy10sm18993813wjb.21.2014.09.30.04.57.54 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Sep 2014 04:57:55 -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 s8UBvrLT079813 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 30 Sep 2014 12:57:54 +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 s8UBvr8f079812; Tue, 30 Sep 2014 12:57:53 +0100 (BST) (envelope-from mexas) Date: Tue, 30 Sep 2014 12:57:53 +0100 (BST) From: Anton Shterenlikht Message-Id: <201409301157.s8UBvr8f079812@mech-as221.men.bris.ac.uk> To: mexas@bristol.ac.uk, wojtek@puchar.net Subject: Re: cluster FS? Reply-To: mexas@bristol.ac.uk In-Reply-To: Cc: freebsd-hackers@freebsd.org 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: Tue, 30 Sep 2014 12:27:02 -0000 >From wojtek@puchar.net Tue Sep 30 12:14:35 2014 > >as disk array presents block devices, not files it is not possible to have >filesystem read write access with more than one computer to the same block >device. >There is no AFAIK filesystems that can communicate between nodes to >synchronize state after writes and prevent conflict. The hardware is inherited from a VMS cluster, which did precisely that. I don't remember now what FS VMS used. I guess I'm trying to replicate a VMS cluster with FreeBSD means. >> I want to have all nodes equal, i.e. no master/slave >> or server/client model. Also, the disk array >> provides adequate RAID already, so that is not > >instead of using disk arrays (expensive) it's better to run FreeBSD as well.. I have a populated array already, so no extra costs are involved. >file server with good deal of disks and connectivity and export >filesystems using eg. NFS. but again, what if the NFS server dies? The data is no longer available. Thanks Anton