On Mon, 28 Jul 2008, Ross wrote: > > TEST1: Opened File Browser, copied the test data to the pool. > Half way through the copy I pulled the drive. THE COPY COMPLETED > WITHOUT ERROR. Zpool list reports the pool as online, however zpool > status hung as expected.
Are you sure that this reference software you call "File Browser" actually responds to errors? Maybe it is typical Linux-derived software which does not check for or handle errors and ZFS is reporting errors all along while the program pretends to copy the lost files. If you were using Microsoft Windows, its file browser would probably report "Unknown error: 666" but at least you would see an error dialog and you could visit the Microsoft knowledge base to learn that message ID 666 means "Unknown error". The other possibility is that all of these files fit in the ZFS write cache so the error reporting is delayed. The Dtrace Toolkit provides a very useful DTrace script called 'errinfo' which will list every system call which reports and error. This is very useful and informative. If you run it, you will see every error reported to the application level. Bob ====================================== Bob Friesenhahn [EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
