Luke Scharf <[EMAIL PROTECTED]> writes: > As for the claims, I don't buy that it's impossible to corrupt a ZFS > volume. I've replicated the demo where the guy dd's /dev/urandom > over part of the disk, and I believe that works -- but there are a > lot of other ways to corrupt a filesystem in the real world. I'm > spending this morning setting up a server to try ZFS in our > environment -- which will put it under a heavy load with a lot of > large files and heavy churn. We'll see what happens!
I've done that one too. It's fun -- and caused me to learn the difference between /dev/random and /dev/urandom :-). It's easy to corrupt the volume, though -- just copy random data over *two* disks of a RAIDZ volume. Okay, you have to either do the whole volume, or get a little lucky to hit both copies of some piece of information before you get corruption. Or pull two disks out of the rack at once. With the transactional nature and rotating pool of top-level blocks, I think it will be pretty darned hard to corrupt a structure *short of* deliberate damage exceeding the redundancy of the vdev. If you succeed, you've found a bug, don't forget to report it! -- David Dyer-Bennet, <mailto:[EMAIL PROTECTED]>, <http://www.dd-b.net/dd-b/> RKBA: <http://www.dd-b.net/carry/> Pics: <http://dd-b.lighthunters.net/> <http://www.dd-b.net/dd-b/SnapshotAlbum/> Dragaera/Steven Brust: <http://dragaera.info/> _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
