> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss- > boun...@opensolaris.org] On Behalf Of Roy Sigurd Karlsbakk > > bash-4.0# mkfile -n 2000000000000 d0 > bash-4.0# zpool create pool $PWD/d0 > bash-4.0# mkfile -n 1992869543936 d1 > bash-4.0# zpool attach pool $PWD/d0 $PWD/d1
As long as you're just doing this for testing, great. I wouldn't suggest a configuration like that for any sort of permanent configuration. Filesystems inside of files ... In general, not a great idea. With only rare exceptions. Also, you know you can do it all on one line, right? zpool create mypool mirror $PWD/d0 $PWD/d1 Do a zpool status next. I think the supposed "resilver" will be basically instantaneous, because the pool is empty. But you should just check, and make sure the pool is healthy and not resilvering before you start your abuse. > r...@mime:/testpool/testdisks# dd if=/dev/urandom of=d1 bs=100k count=1 > skip=30 > 1+0 records in > 1+0 records out > 102400 bytes (102 kB) copied, 0.00208301 s, 49.2 MB/s > r...@mime:/testpool/testdisks# dd if=/dev/urandom of=d0 bs=100k count=1 > skip=50 > 1+0 records in > 1+0 records out > 102400 bytes (102 kB) copied, 0.00205321 s, 49.9 MB/s > > This resulted in a panic - see below for the info from the kernel log. That looks perfect to me, except one thing. You should zpool export before doing those dd's. While ZFS will correctly identify the faulty blocks (and in your case, correct them because you have a mirror) ... If you're doing that to the "device" while it's mounted, I think that's worse than unknown randomness happening on disks that aren't reporting the randomness. I think what you're doing (writing to the file, thus perhaps eliminating the ZFS open file handle to the "device") is causing the "devices" to be swept out from under ZFS's feet. I think this technique is more like a simulation of unplugging disks, and less like a simulation of random undetected errors happening on disks. Also, if you're writing the randomness to blocks that happen to be unoccupied by anything, the system, I believe, won't even notice, because it'll never read the empty space that you've intentionally corrupted. To ensure a good result, I would recommend: Create the filesystem as you've done. Fill up the filesystem. Thus, when you later do a "scrub" it will have to inspect all blocks. zpool export. Perform the dd's from urandom as you've done. zpool import. Check: zpool status (it will probably say no errors) Then zpool scrub. After some time, zpool status will probably show that it found and corrected errors. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
