From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joel Becker Subject: Re: GFS, what's remaining Date: Sun, 4 Sep 2005 15:18:20 -0700 Message-ID: <20050904221820.GB8684@ca-server1.us.oracle.com> References: <20050901104620.GA22482@redhat.com> <20050901035939.435768f3.akpm@osdl.org> <1125586158.15768.42.camel@localhost.localdomain> <20050901132104.2d643ccd.akpm@osdl.org> <20050903051841.GA13211@redhat.com> <20050904203344.GA1987@elf.ucw.cz> Reply-To: linux clustering Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andrew Morton , linux-cluster@redhat.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Alan Cox Return-path: To: Pavel Machek Content-Disposition: inline In-Reply-To: <20050904203344.GA1987@elf.ucw.cz> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-cluster-bounces@redhat.com Errors-To: linux-cluster-bounces@redhat.com List-Id: linux-fsdevel.vger.kernel.org On Sun, Sep 04, 2005 at 10:33:44PM +0200, Pavel Machek wrote: > > - read-only mount > > - "specatator" mount (like ro but no journal allocated for the mount, > > no fencing needed for failed node that was mounted as specatator) > > I'd call it "real-read-only", and yes, that's very usefull > mount. Could we get it for ext3, too? In OCFS2 we call readonly+journal+connected-to-cluster "soft readonly". We're a live node, other nodes know we exist, and we can flush pending transactions during the rw->ro transition. In addition, we can allow a ro->rw transition. The no-journal+no-cluster-connection mode we call "hard readonly". This is the mode you get when a device itself is readonly, because you can't do *anything*. Joel -- "Lately I've been talking in my sleep. Can't imagine what I'd have to say. Except my world will be right When love comes back my way." Joel Becker Senior Member of Technical Staff Oracle E-mail: joel.becker@oracle.com Phone: (650) 506-8127