From: Hayati Ayguen <h_ayguen@web.de>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] tests on (and howto increase) lifetime?
Date: Wed, 14 Jul 2021 14:44:35 +0200 [thread overview]
Message-ID: <d1a34c8a-167f-1cf1-c272-026686ac2f22@web.de> (raw)
Hi,
[ probably i'm wrong in this mailing list .. but this is best, i could
find. also i tried to search archive .. but couldn't find the right topic. ]
i have a logging application on raspberry pi (3/4) writing to an
usb-stick or sd-card through an usb-adapter - not the internal/boot
sd-card with the operating system. see https://groups.io/g/fmlist-scanner
some are used mobile: in a car or backpack.
it's writing approximately 100 - 200 kB data (few new files: some csv
and a zip) every 3 to 5 minutes. write speed/performance is no issue in
my application. the raspberry pi's tends to freeze or reboot from time
to time .. thus the data should be safely stored .. it's sync'ed after
every write (of the few files).
daily data is summarized, compressed, uploaded and moved into another
directory.
vfat formatted usb-sticks usually get broken regularly in some weeks to
several months.
that is why i meanwhile recommend f2fs: looks it behaves better - so far.
are there any tests (scripts or programs) to tests the life
duration/cycles of usb-memory-sticks or sd-cards independent of
filesystem? i would be interested to compare vfat or some other
filesystem vs. f2fs.
is there a safe way to detect write errors - independent of file system
- deactivating the system's cache buffers when test-reading?
are there additional strategies to increase the life of sd-cards?
kind regards,
Hayati
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2021-07-14 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 12:44 Hayati Ayguen [this message]
2021-07-17 8:38 ` [f2fs-dev] tests on (and howto increase) lifetime? Chao Yu
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=d1a34c8a-167f-1cf1-c272-026686ac2f22@web.de \
--to=h_ayguen@web.de \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).