I'm working on testing this some more by doing a savecore -L right after I start the copy.
BTW, I'm copying to a raidz2 of only 5 disks, not 16 (the chassis supports 16, but isn't fully populated). So far as I know, there is no spinup happening - these are not RAID controllers, just dumb SATA JBOD controllers, so I don't think they control drive spin in any particular way. Correct me if I'm wrong, of course. On Wed, Mar 11, 2009 at 11:23 AM, Marc Bevand <m.bev...@gmail.com> wrote: > The copy operation will make all the disks start seeking at the same time and > will make your CPU activity jump to a significant percentage to compute the > ZFS checksum and RAIDZ parity. I think you could be overloading your PSU > because of the sudden increase in power consumption... > > However if you are *not* using SATA staggered spin-up, then the above theory > is unlikely because spinning up consumes much more power than when seeking. > So, in a sense, a successful boot proves your PSU is powerful enough. > > Trying reproducing the problem by copying data on a smaller number of disks. > You tried 2 and 16. Try 8. > > -marc > > _______________________________________________ > 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
