All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@sigma-star.at>
To: Doug Crawford <dcraw101@gmail.com>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: ubifs robustness with early power cut warning
Date: Mon, 02 Oct 2017 18:45:27 +0200	[thread overview]
Message-ID: <7850553.GNXqutYARo@blindfold> (raw)
In-Reply-To: <CAAEsGzKs1kM4TJVKrrsS_GjxQ3kMQa0zwmX2_z3qRpCdS-Xhag@mail.gmail.com>

Am Montag, 2. Oktober 2017, 18:14:28 CEST schrieb Doug Crawford:
> I think my use case might be a little different. This 500 millisecond
> early power down warning is intended to be recoverable if the power is
> restored in that period.  The effect I am looking for is that any new
> fsync or sync commands made during this 500 ms window will pause or
> block, but if the power is restored then the sync will be successful.

Hmm, if I understand your correctly, all you need is freeze/thaw support in 
UBIFS.
Upon power-loss you freeze the filesystem and if power recovers you can thaw 
it.

Does this information help? :-)

Thanks,
//richard

-- 
sigma star gmbh - Eduard-Bodem-Gasse 6 - 6020 Innsbruck - Austria
ATU66964118 - FN 374287y

  reply	other threads:[~2017-10-02 16:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-29 23:20 ubifs robustness with early power cut warning Doug Crawford
2017-09-30 16:19 ` Richard Weinberger
2017-10-02 16:14   ` Doug Crawford
2017-10-02 16:45     ` Richard Weinberger [this message]
2017-10-02 17:33       ` Doug Crawford
2017-10-02 18:03         ` Richard Weinberger
2017-10-02  8:06 ` Kees Trommel
2017-10-02 11:35   ` Richard Weinberger
2017-10-03  6:57     ` Kees Trommel
     [not found]     ` <7b89bbfe-8503-a50a-0271-09d69a99eeec@aimvalley.nl>
2017-10-03  7:26       ` Richard Weinberger

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=7850553.GNXqutYARo@blindfold \
    --to=richard@sigma-star.at \
    --cc=dcraw101@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard.weinberger@gmail.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 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.