From owner-freebsd-geom@FreeBSD.ORG Sat Nov 11 05:42:13 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D031E16A407; Sat, 11 Nov 2006 05:42:13 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9581743D4C; Sat, 11 Nov 2006 05:42:13 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.25] ([192.168.42.25]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id kAB5gAl5027805; Fri, 10 Nov 2006 23:42:10 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <455562B5.7@centtech.com> Date: Fri, 10 Nov 2006 23:42:13 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5.0.7 (X11/20061015) MIME-Version: 1.0 To: Igor Sviridov References: <20061110150957.A14717@seagull.nest.org> In-Reply-To: <20061110150957.A14717@seagull.nest.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2186/Fri Nov 10 22:29:49 2006 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: pjd@freebsd.org, freebsd-geom@freebsd.org Subject: Re: geom s3 class (gs3?) X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Nov 2006 05:42:13 -0000 On 11/10/06 17:09, Igor Sviridov wrote: > hi, > > I guess most people here heard about Amazon S3 storage service: > http://aws.amazon.com/s3 > > I would love to have a Geom class which would use S3 as a back-end. > While S3 api is good one for Web applications, using filesystem > is often simpler and sometimes the only way. > > Obviously mapping filesystem calls to S3 API may be too slow for many > applications but this can be mitigated by adding local write cache/queue > on another geom provider (disk), or modifying gmirror to return write > calls once they're committed to local mirror component (and using it as > queue for remote mirror component stored on S3). > > There is in fact Linux prototype implementation of similar idea, though > on slightly different level - "s3fs" filesystem via FUSE: > > http://dev.extensibleforge.net/wiki/s3/fuse > > and closed-source open-spec JungleDisk: > http://www.jungledisk.com/ Amazon's S3 looks more like a filesystem than a GEOM-like block device. It could be implemented as a very rudimentary file system I suppose. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------