From: David Woodhouse <dwmw2@infradead.org>
To: Fabrizio Pollastri <pollastri@iriti.cnr.it>
Cc: linux-mtd@lists.infradead.org
Subject: Re: "add only" fs
Date: Tue, 12 Jun 2001 11:23:02 +0100 [thread overview]
Message-ID: <18752.992341382@redhat.com> (raw)
In-Reply-To: <3B25EBA0.71C2EF64@iriti.cnr.it>
pollastri@iriti.cnr.it said:
> a common problem in embedded systems is to log important data in a way
> safe against power failure and software bugs. The question is: may be
> jffs2 the right place to introduce an "add only" protection? It can be
> at partition level, in such a way that mounting that partition as "add
> only" I am protected against loss of data, because I can only create
> new files and/or append data to existing files and never delete or
> truncate a file unless the partition is remounted rw.
JFFS2 _has_ to move data around, even data which haven't changed. If you
want 100% guarantees (or as close as possible) that some parts can't
change, put them in a separate partition which you mount readonly.
--
dwmw2
prev parent reply other threads:[~2001-06-12 10:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 10:14 "add only" fs Fabrizio Pollastri
2001-06-12 10:23 ` David Woodhouse [this message]
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=18752.992341382@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=pollastri@iriti.cnr.it \
/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