From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jamie Lokier Subject: Re: [osd-dev] [PATCH 1/9] exofs: osd Swiss army knife Date: Tue, 13 Jan 2009 15:09:55 +0000 Message-ID: <20090113150955.GA9636@shareable.org> References: <4947BFAA.4030208@panasas.com> <4947C624.3050602@panasas.com> <4964CEA4.7080001@panasas.com> <20090113135526.28730314@lxorguk.ukuu.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Benny Halevy , Boaz Harrosh , open-osd development , Avishay Traeger , Jeff Garzik , Andrew Morton , Al Viro , linux-fsdevel , linux-kernel To: Alan Cox Return-path: Received: from mail2.shareable.org ([80.68.89.115]:39511 "EHLO mail2.shareable.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751958AbZAMPKX (ORCPT ); Tue, 13 Jan 2009 10:10:23 -0500 Content-Disposition: inline In-Reply-To: <20090113135526.28730314@lxorguk.ukuu.org.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Alan Cox wrote: > > > +#define EXOFS_SUPER_ID 0x10000 /* object ID for on-disk superblock */ > > And if an OS failure breaks the super block and you have only one how do > you recover it ? Having one super block would be silly. But aren't most kinds of replication better done behind the OSD level, on the storage fabric? OSD is all about letting the fabric decide things like allocation and durability strategies after all. With multiple super blocks at the filesystem level, some OS failures that would trash one of the super blocks would simply trash all the copies. I wonder how much less likely trashing one super block object than trashing a set of them would be. -- Jamie