Depends on your definition of firmware. In higher end arrays the data
is checksummed when it comes in and a hash is written when it gets to
disk. Of course this is no where near end to end but it is better then
nothing.
... and code is code. Easier to debug is a context sensitive term.
Its unfortunate that so many posts hung about the code,
Its the design that protects your data and with ZFS you have a better
design for
data integrity. If the code is faulty and now thats a bug. And design
should protect you
unless your error detection and correction logic is faulty.
(I mean this is like anti-corruption buereau being corrupt :-)).
There is a huge difference between ability to detect corruption versus
not knowing
that data is corrupted at all.
Now if the code is upto design or not, is what real world testing shows,
in most of the cases ZFS should help.
Kiran
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
