From: danielhilst@gmail.com (Daniel Hilst Selli)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Filesystem and files getting corrupted
Date: Mon, 24 Jun 2013 17:08:56 -0300 [thread overview]
Message-ID: <51C8A758.8030602@gmail.com> (raw)
I'm working on an embedded project based on var-som-am35 from TI. [1]
I experiencing a lot of corruption from files and even the entire
filesystem... is there any guide on how debug filesystems corruption?
We already tryied vfat and ext3 fs.. changed media, changed machines...
The filesystem runs on mmc card, or on usb flash drive... There is a
java aplication running on top of this filesystem, which uses JMS, that
is very I/O agressive..
Cheers,
next reply other threads:[~2013-06-24 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 20:08 Daniel Hilst Selli [this message]
2013-06-25 10:28 ` Filesystem and files getting corrupted María Soler Heredia
2013-06-25 16:02 ` Valdis.Kletnieks at vt.edu
2013-06-25 14:52 ` Manish Katiyar
2013-07-04 0:24 ` Peter Teoh
2013-07-07 22:13 ` Daniel Hilst Selli
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=51C8A758.8030602@gmail.com \
--to=danielhilst@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).