From: Peter Teoh <htmldeveloper@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Peter Teoh <htmldeveloper@gmail.com>,
kernelnewbies <kernelnewbies@nl.linux.org>,
linux-fsdevel@vger.kernel.org, ext3-users@redhat.com
Subject: "Write once only but read many" filesystem
Date: Sat, 22 Mar 2008 12:39:32 +0800 [thread overview]
Message-ID: <47E48D84.7070701@gmail.com> (raw)
In-Reply-To: <20080314232403.GI3542@webber.adilger.int>
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.
next prev parent reply other threads:[~2008-03-22 4:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 16:17 filesystem differentiation Peter Teoh
2008-03-14 23:24 ` Andreas Dilger
2008-03-22 4:39 ` Peter Teoh [this message]
[not found] ` <20080322102331.GA19347@logfs.org>
[not found] ` <804dabb00803220752h670757d8o9c1b7fa3696467bc@mail.gmail.com>
[not found] ` <20080322150626.GB19347@logfs.org>
2008-03-22 15:55 ` "Write once only but read many" filesystem Peter Teoh
2008-03-22 16:59 ` Jörn Engel
2008-03-24 4:49 ` Scott Lovenberg
2008-03-24 6:35 ` Peter Teoh
-- strict thread matches above, loose matches on Subject: below --
2008-03-24 6:45 Peter Teoh
2008-03-24 16:56 ` Bryan Henderson
2008-03-25 0:47 ` Peter Teoh
2008-03-25 15:22 ` Matthew Wilcox
2008-03-25 18:42 ` Bryan Henderson
2008-03-25 18:32 ` Bryan Henderson
2008-03-26 2:27 ` Peter Teoh
2008-03-26 16:49 ` Bryan Henderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47E48D84.7070701@gmail.com \
--to=htmldeveloper@gmail.com \
--cc=ext3-users@redhat.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).