From: David Woodhouse <dwmw2@infradead.org>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: Marco Braga <marco.braga@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: JFFS2 losing files on mount
Date: Thu, 22 Jan 2009 17:36:46 +1100 [thread overview]
Message-ID: <1232606206.7422.6.camel@macbook.infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0901220725490.1706@lnxricardw.se.axis.com>
On Thu, 2009-01-22 at 07:33 +0100, Ricard Wanderlof wrote:
> On Thu, 22 Jan 2009, David Woodhouse wrote:
>
> >> We use JFFS2 on both an ARM9-platform and on our own CRIS platform. We
> >> never unmount the device in preparation for power down; when someone pulls
> >> the plug, the system just dies. While we do occasionally see warning
> >> messages about incomplete nodes during the next boot-up, we have never
> >> experienced anything as severe as you mention, and we have not lost any
> >> files on the JFFS2 filesystem either.
> >
> > Is this on NAND, or NOR flash? On NAND flash, you do actually have to
> > have non-buggy userspace; if you don't use sync() or fsync()
> > appropriately then there may be data which aren't yet flushed to the
> > flash.
>
> To be more specific, on NOR flash we never say any messages about bad data
> nodes. With NAND flashes we do. However, we have never experienced missing
> files the way Marco seems to have.
>
> What's the situation though, assuming one doesn't use sync()/fsync(),
> I can understand that data won't get flushed properly, but would that
> result in a file being lost?
Not unless the file was only just created, and you lose power before
that creation hits the medium.
> In our case, the device may be powered down at any time. Let's assume an
> application has a lot of data to write, using several write() calls. I can
> envisage two scenarios:
> 1. Userspace app writes all data, but fails to call sync/fsync before
> power fails.
> 2. Userspace app writes some of its data, but power fails before it
> has time to write all.
>
> In both cases I would imagine that the end result is the same - all data
> is not written to the flash because the plug is pulled. Considering the
> data in the file, it doesn't matter if it wasn't written out by JFFS2 or
> becuase the application died to early. Or is this a faulty assumption?
No, you're quite right.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
prev parent reply other threads:[~2009-01-22 6:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 9:29 JFFS2 losing files on mount Marco Braga
2009-01-21 15:05 ` Ricard Wanderlof
2009-01-22 4:03 ` David Woodhouse
2009-01-22 6:33 ` Ricard Wanderlof
2009-01-22 6:36 ` 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=1232606206.7422.6.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marco.braga@gmail.com \
--cc=ricard.wanderlof@axis.com \
/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