From: Artem Bityutskiy <dedekind1@gmail.com>
To: Daniel Wagener <daniel.wagener@kernelconcepts.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Subject: UBIFS and small dynamic files
Date: Tue, 25 Oct 2011 10:52:43 +0300 [thread overview]
Message-ID: <1319529170.14178.10.camel@golum> (raw)
In-Reply-To: <4EA1823D.3040708@kernelconcepts.de>
[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]
On Fri, 2011-10-21 at 16:31 +0200, Daniel Wagener wrote:
> Ahoi,
>
> we are having trouble with the side effects of the UBIFS write buffer
> described in http://www.linux-mtd.infradead.org/doc/ubifs.html#L_writebuffer
> We have certain config files that are quite small and get rewritten very
> frequently by their applications.
> Matchbox-panels' ~/.matchbox/mbdock.session is a fine example as it gets
> emptied on a power cut or hard reset resulting in an empty and therefore
> useless panel on the next start.
Well, all the docs about the synchronization are at the web site. There
is also a description with links of what other FSes do:
http://linux-mtd.infradead.org/doc/ubifs.html#L_sync_exceptions
>
> The document above mentions the '-o sync' option which disables the
> write buffer on a partition, but this is not an option for us because we
> do not want to reduce the write performance. And there is also the issue
> of a synchronously mounted UBIFS that can make things even worse in case
> of power cuts.
You can do fsync(), or you can set the "S" flag to the file and make it
always be synchronous (see man chattr).
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2011-10-25 7:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 14:31 Subject: UBIFS and small dynamic files Daniel Wagener
2011-10-24 3:21 ` Jon Povey
2011-10-28 14:03 ` Artem Bityutskiy
2011-10-25 7:52 ` Artem Bityutskiy [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=1319529170.14178.10.camel@golum \
--to=dedekind1@gmail.com \
--cc=daniel.wagener@kernelconcepts.de \
--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