On Thu, Mar 06, 2008 at 06:25:21PM -0800, David Pacheco wrote: > Stuart Anderson wrote: > > > >It is also interesting to note that this system is now making negative > >progress. I can understand the remaining time estimate going up with > >time, but what does it mean for the % complete number to go down after > >6 hours of work? > > > >Thanks. > > > > > ># zpool status | egrep -e "progress|errors" ; date > > scrub: scrub in progress, 75.49% done, 28h51m to go > >errors: No known data errors > >Thu Mar 6 08:50:59 PST 2008 > > > ># zpool status | egrep -e "progress|errors" ; date > > scrub: scrub in progress, 75.24% done, 31h20m to go > >errors: No known data errors > >Thu Mar 6 15:15:39 PST 2008 > > > > > There are a few things which may cause the scrub to restart. See: > > 6655927 zpool status causes a resilver or scrub to restart > 6343667 scrub/resilver has to start over when a snapshot is taken > > Sorry the latter doesn't have a useful description, but the synopsis > says it all: taking snapshots causes scrubs to restart. Either of these > may explain the "negative progress." >
I have confirmed that "zpool status" run as root does not reset the counter on this system, and no snapshots where made since the scrub was started. For what it is worth, this system has now made it to, # /usr/sbin/zpool status | egrep -e "progress|errors" ; date scrub: scrub in progress, 92.05% done, 10h4m to go errors: No known data errors Fri Mar 7 12:41:44 PST 2008 The kernel is at 1% CPU utilization and the disks in the pool are only 10% busy (iostat). So it is making progress, but I am still confused about what resource is blocking faster progress. Thanks. -- Stuart Anderson [EMAIL PROTECTED] http://www.ligo.caltech.edu/~anderson _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
