> I don't know about jpg's, you may be right.
The business about one bit sh.tting an entire file is a very low
probability event -- there isn't much metadata in a JPEG or even RAW
file, and not much of that is super-critical to the point that one bit
prevents decoding.
An SEU mid-stream can cause the decoder to lose sync, resulting in crud
thereafter. You can hexedit a few JPEG's to see what happens. (For a
color JPEG, there are three encoded chunks, and an SEU in one chunk
only effects that chunk, though the visible result is from that point
in the image on to the end.)
> But as a programmer, I would be stunned if a single bit could bring
> down a file system. Even MS-DOS's file system (FAT16 ? - don't
[quoted text clipped - 4 lines]
> proceeded to ignore it, requiring a 3rd party utility to fix it with no
> difficulty).
Modern filesystems are indeed more robust than people around here
think: a single bit error just won't be able to render an FS unusable
or unfixable. The main problem is the physical destruction of the
information substrate. And no carry-on xray machine will come close to
doing this to a flash memory device.
> Believing a file system that today typically stores 100 to 500 times as
> much as my first hard drive without built-in error correction is simply
> beyond me.
Maybe Mythbusters accepts submissions? Wouldn't make for an exciting
episode though, rolling CF or SD cards through an xray machine or
twiddling bits in filesystems. Mind you, though, they did do one about
mag-stripes being erased by "eel skin wallets" (the sh.t people
believe!). Long segment with Adam sitting there trying his best to
destroy a mag-stripe on some cards. In the end they gad to build, in
effect, a powerful degausser. What would they make for a CF destroyer?
David J Taylor - 30 Dec 2005 21:42 GMT
[]
> The business about one bit sh.tting an entire file is a very low
> probability event -- there isn't much metadata in a JPEG or even RAW
[quoted text clipped - 6 lines]
> chunk only effects that chunk, though the visible result is from that
> point in the image on to the end.)
Yes, I've seen exactly that effect, although on a JPEG which had been sent
over a radio link.
> Modern filesystems are indeed more robust than people around here
> think: a single bit error just won't be able to render an FS unusable
> or unfixable. The main problem is the physical destruction of the
> information substrate. And no carry-on xray machine will come close
> to doing this to a flash memory device.
.. and FAT-16 is a modern file system?
Having said that, I haven't seen any problems with taking CF or SD cards
through hand-baggage inspections, and would have no hesitation in so
doing.
David
Jim Redelfs - 31 Dec 2005 03:46 GMT
> a powerful degausser. What would they make for a CF destroyer?
My guess would be your "powerful degausser". There's a big difference between
X-ray and a magnetic field. I suspect a powerful magnet would nuke a CF card.
:)
JR
>>> Even if there was damage, it would typically be limited to a single
>>> bit, and therefore a single pixel.
[quoted text clipped - 24 lines]
>
> Austin
The error correction is there, built into the hard disk itself. Yes,
modern file systems try harder to prevent data loss in critical regions
from damaging the file system, but we all know it can and does happen.
As the memory card is typically used as a data-only card, some single-bit
errors might not stop it being read by a third-party utility, as you say.
Some errors in the boot block code, for example, would not matter. What
about any master partition table? And recall that I said "possibly".
David