From: Goffredo Baroncelli <kreijack@inwind.it>
To: Hegner Robert <rhegner@hsr.ch>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs raid1 filesystem on sdcard corrupted
Date: Thu, 25 Feb 2016 22:35:43 +0100 [thread overview]
Message-ID: <56CF73AF.70301@inwind.it> (raw)
In-Reply-To: <nank09$nad$1@ger.gmane.org>
Hi Robert,
On 2016-02-25 20:18, Hegner Robert wrote:
[...]
> So, in your experience 1) Which are the SDcards we can trust in?
> (brand? model?)
For this kind of use you should look to an "industrial grade" SD cards. But these are quite expensive (we are talking about 50€ for 4GB....). Our supplier suggested us the ATP sd cards [*].
I tested a NON industrial grade sdcard with simulated power failure; my test showed that this card fails quite early (about hundreds of cycles).
I have to point out that "industrial grade" is a generic definition. Unfortunately I was unable to find a more detailed spec.
> 2) What would be a better way (with or without the use of btrfs) to
> make an embedded system more robust against power failures and
> flash-memory-wearing?
If it is possible to avoid don't write on the storage Don't log. Leave the filesystem "read only" and switch to read/write only when you have to write; after the write re-switch the filesystem RO. This cannot prevent the damage of the card, but could reduce the likelihood of the damage.
I never tested the internal flash of these boards. May be that this flash is more reliable...
BR
G.Baroncelli
[*] "http://www.digikey.com/product-search/en?mpart=AF8GUDI-OEM&vendor=1282"
--
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2016-02-25 21:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 17:34 btrfs raid1 filesystem on sdcard corrupted Hegner Robert
2016-02-25 17:44 ` Hegner Robert
2016-02-25 18:08 ` Lionel Bouton
2016-02-25 19:18 ` Hegner Robert
2016-02-25 19:53 ` Chris Murphy
2016-02-25 21:35 ` Goffredo Baroncelli [this message]
2016-02-26 7:53 ` Hegner Robert
2016-02-25 19:32 ` Chris Murphy
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=56CF73AF.70301@inwind.it \
--to=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=rhegner@hsr.ch \
/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.