Yuvraj, I see that you are using files as disks. You could write a few random bytes to one of the files and that would induce corruption. To make a particular disk faulty you could mv the file to a new name.
Also, you can explore the zinject from zfs testsuite . Probably it has a way to induce fault. Thanks and regards, Sanjeev yuvraj wrote: > Hi Sanjeev, > I am herewith giving all the details of my zpool by > firirng #zpool status command on commandline. Please go through the same and > help me out. > > Thanks in advance. > > > Regards, > Yuvraj > Balkrishna Jadhav. > > ================================================================== > > # zpool status > pool: mypool1 > state: ONLINE > scrub: none requested > config: > > NAME STATE READ WRITE CKSUM > mypool1 ONLINE 0 0 0 > /disk1 ONLINE 0 0 0 > /disk2 ONLINE 0 0 0 > > errors: No known data errors > > pool: zpool21 > state: ONLINE > scrub: scrub completed with 0 errors on Sat Oct 18 13:01:52 2008 > config: > > NAME STATE READ WRITE CKSUM > zpool21 ONLINE 0 0 0 > /disk3 ONLINE 0 0 0 > /disk4 ONLINE 0 0 0 > > errors: No known data errors > -- > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
