From: Piotr Trojanek <ptroja@elproma.com.pl>
To: linux-mtd@lists.infradead.org
Subject: Re: Question about power fail during file upgrade
Date: Mon, 30 Sep 2002 10:02:33 +0200 [thread overview]
Message-ID: <20020930080233.GA1236@elproma.com.pl> (raw)
In-Reply-To: <8493.1033029923@redhat.com>
On Thu, Sep 26, 2002 at 09:45:23AM +0100, David Woodhouse wrote:
>
> Kschoo70C@netscape.net said:
> > I need some help to understand how the JFFS2 works. If I have a
> > version 1 of software component A on JFFS2, what happen if power
> > failed while I am in the middle of upgrading the component A to
> > version 2 ? The question is do I have version 1 intact or a
> > combination of version 1 and 2 ?
>
> > Does the JFFS2 filesystem only set the inodes of a file to be valid
> > only after a complete file is written to the flash ? Does the old file
> > will only be deleted only after the new file is verified to be valid ?
>
> JFFS2 knows nothing of 'complete files'. You are guaranteed atomicity of
> individual file system operations only, according to POSIX.
>
> As with other file systems, you can write the new version of the file, then
> rename it over the top of the original. That will be atomic.
>
> There's been talk about extending JFFS2 to allow userspace 'transactions'
> but it's not been done.
so the only atomic change, that is guaranteed to work is renaming
new.file -> old.file?
if I need to make upgrade which depends on 10 files what should I do?
how about put all filesystem in one .tar and put it in ramdisk at system
startup, then make upgrade of .tar file, which is on JFFS2 DOC and
reboot? will it work?
--
Piotr Trojanek
next prev parent reply other threads:[~2002-09-30 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 8:38 Question about power fail during file upgrade Kschoo70C
2002-09-26 8:45 ` David Woodhouse
2002-09-30 8:02 ` Piotr Trojanek [this message]
2002-09-30 8:38 ` David Woodhouse
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=20020930080233.GA1236@elproma.com.pl \
--to=ptroja@elproma.com.pl \
--cc=linux-mtd@lists.infradead.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