From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Teoh Subject: "Write once only but read many" filesystem Date: Sat, 22 Mar 2008 12:39:32 +0800 Message-ID: <47E48D84.7070701@gmail.com> References: <804dabb00803140917o2abebd2dh12c77b21a48094c4@mail.gmail.com> <20080314232403.GI3542@webber.adilger.int> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Peter Teoh , kernelnewbies , linux-fsdevel@vger.kernel.org, ext3-users@redhat.com To: unlisted-recipients:; (no To-header on input) Return-path: Received: from wa-out-1112.google.com ([209.85.146.180]:45886 "EHLO wa-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750938AbYCVE2M (ORCPT ); Sat, 22 Mar 2008 00:28:12 -0400 Received: by wa-out-1112.google.com with SMTP id v27so2015867wah.23 for ; Fri, 21 Mar 2008 21:28:10 -0700 (PDT) In-Reply-To: <20080314232403.GI3542@webber.adilger.int> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: For reasons of auditability/accountability, I would like a filesystem such that I can write to it only ONCE, subsequently not modifiable/deletable, but always readable. Kind of a database journal logs - it is continuously being written, sequentiall appending, but not circular buffer based, so that upon running out of space, logging will be paused in memory, and after new storage devices added to it, it will continue to flush out whatever is outstanding in memory. Can ext3 / ext4 or current jbd2 be easily configured to serve this purpose? Thanks.