From: gianluca <gianlucarenzi-RMR/+jklkADqD7ZJT3/+rDUZDU+1vuVT@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Hello list!
Date: Wed, 12 Feb 2014 11:16:10 +0100 [thread overview]
Message-ID: <52FB49EA.30004@eurekelettronica.it> (raw)
Hello list!
I am working on a selfmade board with ARM9 and eMMC as storage.
The final product will be a logger (from solar-inverter, to bus-logger,
etc.,...) so I choose a rootfilesystem with NILFS2.
The distro is a deboostrap based for ARMEL Debian Wheezy 7.2.
I changed the critical filesystem folders (/var, /var/log, /tmp...) to
be tempfs in ram for obviously reasons and the rootfilesystem is nilfs2
based with a noatime option activated.
The protection period is set at 60 seconds because the application can
write data even in shorter periods, but 60 seconds it is a average value
to have a disk-full problem away from normal-user.
What about the wear-leveling of this configuration of the eMMC device?
Can you point me on some tools, utilities to check out this issue?
Best regards,
--
,,,
(o o)
======oOO==(_)==OOo======
Gianluca Renzi
R&D
phone: +39.0542.609120
fax: +39.0542.609212
.oooO Oooo.
======( )==( )=======
\ ( ) /
\_) (_/
===================
| I would like to |
| fix the world, |
| but they're not |
| giving me the |
\ source code! /
---------------
¯\_(".)_/¯
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2014-02-12 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 10:16 gianluca [this message]
[not found] ` <52FB49EA.30004-RMR/+jklkADqD7ZJT3/+rDUZDU+1vuVT@public.gmane.org>
2014-02-12 13:04 ` Hello list! Clemens Eisserer
[not found] ` <CAFvQSYTuM7Zjfz47UGU3KnTgH1iSRWiiZ3iSqXUiu7MKFnOmFA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-12 14:16 ` gianluca
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=52FB49EA.30004@eurekelettronica.it \
--to=gianlucarenzi-rmr/+jklkadqd7zjt3/+rduzdu+1vuvt@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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