On 13. jan.. 2009, at 04.15, Matthew Dillon wrote:
I've seen uncaught data corruption on older machines, but not in
the
last few years. Ah, the days of IDE cabling problems, remembered
fondly (or not). I've seen bad data get through TCP connections
uncaught! Yes, it actually
Hi,
I'm curious if RAID 1 (mirroring) really helps to protect data loss. Of
course if a whole disk dies, RAID 1 has the advantage that
I have an identical copy. But what happens if only a sector of one disk
contains bad data. How can the RAID controller decide which is the
correct sector? Or
nntp.dragonflybsd.org mneum...@ntecs.de wrote in message
news:496b8121$0$881$415eb...@crater_reader.dragonflybsd.org...
Hi,
I'm curious if RAID 1 (mirroring) really helps to protect data loss. Of
course if a whole disk dies, RAID 1 has the advantage that
I have an identical copy. But what
On 2009-01-12 21:37, Konstantinos Pachnis wrote:
On Jan 12, 2009, at 9:13 PM, Gergo Szakal wrote:
nntp.dragonflybsd.org mneum...@ntecs.de wrote in message
news:496b8121$0$881$415eb...@crater_reader.dragonflybsd.org
...
Hi,
I'm curious if RAID 1 (mirroring) really helps to protect data
On Tue, Jan 13, 2009 at 9:20 AM, Simon 'corecode' Schubert
corec...@fs.ei.tum.de wrote:
You're assuming fail-stop errors. If it is a sneaking bit error or
something else, it won't notice.
Ever since ZFS was announced I've wondered how often this actually
happens. So far I've only heard of one
:But Hammer won't notify this as well, right? IIRC, Hammer does CRC only
:on meta-data.
:
:Regards,
:
: Michael
HAMMER CRC's both data and meta-data. The meta-data is self-CRC'd,
however, which is one step down from what ZFS does. ZFS uses
recursive check data, creating an
I've seen uncaught data corruption on older machines, but not in the
last few years. Ah, the days of IDE cabling problems, remembered
fondly (or not). I've seen bad data get through TCP connections
uncaught! Yes, it actually does happen, even more so now that OS's
are
:I confess that, lacking ZFS, I have a very paranoid strategy on my
:Linux machines for doing backups (of code workspaces, etc). I archive
:the code onto a tmpfs and checksum that, and from the tmpfs distribute
:the archive and checksum to local and remote archives. This avoids the
:unthinkably
