From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: single-file file system? Date: Fri, 24 Sep 2004 21:44:25 +0100 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20040924214425.A31697@infradead.org> References: <200409242026.i8OKQDVE010037@agora.fsl.cs.sunysb.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org Return-path: Received: from imladris.demon.co.uk ([193.237.130.41]:22290 "EHLO phoenix.infradead.org") by vger.kernel.org with ESMTP id S269140AbUIXUo1 (ORCPT ); Fri, 24 Sep 2004 16:44:27 -0400 To: Erez Zadok Content-Disposition: inline In-Reply-To: <200409242026.i8OKQDVE010037@agora.fsl.cs.sunysb.edu>; from ezk@cs.sunysb.edu on Fri, Sep 24, 2004 at 04:26:13PM -0400 List-Id: linux-fsdevel.vger.kernel.org On Fri, Sep 24, 2004 at 04:26:13PM -0400, Erez Zadok wrote: > I have a need for a very simple f/s that supports only one file on a raw > device, starting from the beginning of the device and growing until possibly > its end. The reason for this simple f/s is to minimize the overhead for > certain applications that don't need more than one large file, but cannot > use a raw device directly (i.e., they expect a f/s interface). Do you know > of any f/s that does that for Linux? We actually have a filesystem that represents blockdevices as single big file in fs/block_dev.c. It's just not mountable.