From: Daniel Wagener <daniel.wagener@kernelconcepts.de>
To: linux-mtd@lists.infradead.org
Subject: Subject: UBIFS and small dynamic files
Date: Fri, 21 Oct 2011 16:31:25 +0200 [thread overview]
Message-ID: <4EA1823D.3040708@kernelconcepts.de> (raw)
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.
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.
Has there been any further development to these issues since 2008?
next reply other threads:[~2011-10-21 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 14:31 Daniel Wagener [this message]
2011-10-24 3:21 ` Subject: UBIFS and small dynamic files Jon Povey
2011-10-28 14:03 ` Artem Bityutskiy
2011-10-25 7:52 ` 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=4EA1823D.3040708@kernelconcepts.de \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.