From: tommy <jiujin.hong@mid-fun.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: about ubifs
Date: Mon, 08 Jun 2009 09:52:45 +0800 [thread overview]
Message-ID: <1244425965.7627.0.camel@tommy-desktop> (raw)
In-Reply-To: <20090608013528.GI15426@shareable.org>
yes,i have do it !
thanks for all !
Tommy
On 一, 2009-06-08 at 02:35 +0100, Jamie Lokier wrote:
> Corentin Chary wrote:
> > On Fri, Jun 5, 2009 at 3:03 PM, tommy<jiujin.hong@mid-fun.com> wrote:
> > > no,i didn't fsync when i close file !
> > >
> > > did ubifs driver can achieve "fsync" when user modify some file and
> > > close with save ?
> >
> > For critical data, you need to call fsync to be sure the data is
> > stored on the flash.
> > There is also a "sync" option for ubifs, but this will hurt performance a lot.
>
> That reminds me.
>
> A filesystem-generic "sync-on-close" mount option would be handy for
> things like that.
>
> Expecting users to call fsync from a shell script is probably a bit much
> in a lot of applications.
>
> -- Jamie
>
next prev parent reply other threads:[~2009-06-08 1:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 12:13 about ubifs tommy
2009-06-05 12:42 ` Corentin Chary
2009-06-05 13:03 ` tommy
2009-06-05 14:04 ` Corentin Chary
2009-06-08 1:35 ` Jamie Lokier
2009-06-08 1:52 ` tommy [this message]
2009-06-08 5:49 ` Artem Bityutskiy
2009-06-08 12:01 ` Jamie Lokier
2009-06-08 12:16 ` Artem Bityutskiy
2009-06-08 12:29 ` Jamie Lokier
2009-06-08 13:30 ` Artem Bityutskiy
2009-06-05 16:26 ` Artem Bityutskiy
-- strict thread matches above, loose matches on Subject: below --
2008-07-08 9:08 About UBIFS Qiang Wang
2008-07-08 9:08 ` Artem Bityutskiy
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=1244425965.7627.0.camel@tommy-desktop \
--to=jiujin.hong@mid-fun.com \
--cc=jamie@shareable.org \
--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