From: pwaechtler@mac.com (Peter Wächtler)
To: linux-arm-kernel@lists.infradead.org
Subject: since when does ARM map the kernel memory in sections?
Date: Wed, 13 Apr 2011 20:35:55 +0200 [thread overview]
Message-ID: <201104132035.55362.pwaechtler@mac.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1104131128070.24613@xanadu.home>
Am Mittwoch, 13. April 2011, 17:44:09 schrieb Nicolas Pitre:
> On Wed, 13 Apr 2011, Peter W?chtler wrote:
> > Am Dienstag, 12. April 2011, 21:20:14 schrieb Andrei Warkentin:
> > > How are you mounting your rootfs and what file system are you using?
> > > What sort of corruptions to the super block are you seeing?
> >
> > It's using ext4 with metadata journalling in ordered mode.
> > I had to check "if it's the FS" - the test programs create lots of
> > directories and files while a timer is armed to issue a soft reset.
> > The partitions where the "stress tests" run on - survive it happily -
> > just the rootfs where almost nothing gets written is severly damaged so
> > that fsck.ext4 will not repair it automatically.
>
> SD cards are doing their own wear leveling internally and you have no
> control over it. Some blocks of data may be moved around, affecting a
> separate logical partition, even if you are not actively writing to that
> partition. Now if you cut power or reset the card while this is
> happening you'll certainly end up with data loss. Those SD cards are
> made to be both cheap and fast, meaning they're certainly not reliable
> with regards to unexpected interruptions.
>
> Furthermore, you should have a look at this article and referenced
> material: http://lwn.net/Articles/428584/.
>
>
Yes, I know this article - and I know about wear levelling etc.
Data loss is not the biggest problem. The capacity is huge (>>4GB) - therefore
I wouldn't want to miss journalling - but I was not involved on the decision.
Ten years ago I carefully ordered the fsync, rename on ext2 on a 64MiB
CompactFlash - worked well enough.
The vendor knows about the requirements - perhaps learned it with another
customer ;)
I tried to "smash" the FS without success in the past - but the rootfs was
mounted via NFS ;) And the partitions that get tortured stay intact - of
course you can say that the wear levelling switches some blocks - but I don't
buy it.
Thanks for all the nice work on Linux - Russell included ;)
Peter
next prev parent reply other threads:[~2011-04-13 18:35 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 18:52 since when does ARM map the kernel memory in sections? Peter Wächtler
2011-04-12 19:11 ` Colin Cross
2011-04-13 18:19 ` Peter Wächtler
2011-04-12 19:20 ` Andrei Warkentin
2011-04-12 20:33 ` Jamie Lokier
2011-04-13 15:27 ` Nicolas Pitre
2011-04-13 20:11 ` Jamie Lokier
2011-04-18 13:52 ` Pavel Machek
2011-04-18 17:07 ` Jamie Lokier
2011-04-18 17:17 ` Nicolas Pitre
2011-04-22 15:47 ` Pavel Machek
2011-04-23 9:23 ` Linus Walleij
2011-04-26 10:33 ` Per Forlin
2011-04-26 19:00 ` Peter Waechtler
2011-04-26 19:07 ` Jamie Lokier
2011-04-26 20:38 ` MMC and reliable write - was: " Peter Waechtler
2011-04-26 22:45 ` Jamie Lokier
2011-04-27 1:13 ` Andrei Warkentin
2011-04-27 13:07 ` Jamie Lokier
2011-04-27 19:18 ` Andrei Warkentin
2011-04-27 19:33 ` Arnd Bergmann
2011-05-03 8:04 ` Jamie Lokier
2011-06-06 10:28 ` Pavel Machek
2011-06-06 20:38 ` Peter Waechtler
2011-04-26 20:24 ` Andrei Warkentin
2011-04-26 22:58 ` Jamie Lokier
2011-04-27 0:27 ` Andrei Warkentin
2011-04-27 13:19 ` Jamie Lokier
2011-04-27 13:32 ` Arnd Bergmann
2011-04-27 18:50 ` Peter Waechtler
2011-04-27 18:58 ` Andrei Warkentin
2011-04-18 19:21 ` Peter Waechtler
2011-04-18 17:24 ` Pavel Machek
2011-04-19 0:43 ` Jamie Lokier
2011-04-13 6:51 ` Peter Wächtler
2011-04-13 15:44 ` Nicolas Pitre
2011-04-13 18:35 ` Peter Wächtler [this message]
2011-04-12 20:15 ` Russell King - ARM Linux
-- strict thread matches above, loose matches on Subject: below --
2011-04-28 20:26 Peter Waechtler
2011-04-28 21:38 ` Andrei Warkentin
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=201104132035.55362.pwaechtler@mac.com \
--to=pwaechtler@mac.com \
--cc=linux-arm-kernel@lists.infradead.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 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.