I ran a scrub on a Solaris 10 update 8 system yesterday and it is 100% done, but not complete: scrub: scrub in progress for 23h57m, 100.00% done, 0h0m to go Any ideas? -- Ian.
On Wed, Mar 17, 2010 at 2:03 PM, Ian Collins <ian at ianshome.com> wrote:> I ran a scrub on a Solaris 10 update 8 system yesterday and it is 100% > done, but not complete: > > scrub: scrub in progress for 23h57m, 100.00% done, 0h0m to go > > Any ideas?I''ve had that happen on FreeBSD 7-STABLE (post 7.2 release) using ZFSv13. scrub showed 100% complete, but "in progress" and timer kept increasing. After waiting an hour, I did a "zpool scrub -s" and then a "zpool scrub". This second scrub finished quicker, and finished completely. No idea why it happened, or why that fixed it. -- Freddie Cash fjwcash at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100317/43bb59ec/attachment.html>
On 03/17/10 14:03, Ian Collins wrote:> I ran a scrub on a Solaris 10 update 8 system yesterday and it is 100% > done, but not complete: > > scrub: scrub in progress for 23h57m, 100.00% done, 0h0m to goDon''t panic. If "zpool iostat" still shows active reads from all disks in the pool, just step back and let it do its thing until it says the scrub is complete. There''s a bug open on this: 6899970 scrub/resilver percent complete reporting in zpool status can be overly optimistic scrub/resilver progress reporting compares the number of blocks read so far to the number of blocks currently allocated in the pool. If blocks that have already been visited are freed and new blocks are allocated, the seen:allocated ratio is no longer an accurate estimate of how much more work is needed to complete the scrub. Before the scrub prefetch code went in, I would routinely see scrubs last 75 hours which had claimed to be "100.00% done" for over a day. - Bill
On 03/18/10 11:09 AM, Bill Sommerfeld wrote:> On 03/17/10 14:03, Ian Collins wrote: >> I ran a scrub on a Solaris 10 update 8 system yesterday and it is 100% >> done, but not complete: >> >> scrub: scrub in progress for 23h57m, 100.00% done, 0h0m to go > > Don''t panic. If "zpool iostat" still shows active reads from all > disks in the pool, just step back and let it do its thing until it > says the scrub is complete. > > There''s a bug open on this: > > 6899970 scrub/resilver percent complete reporting in zpool status can > be overly optimistic > > scrub/resilver progress reporting compares the number of blocks read > so far to the number of blocks currently allocated in the pool. > > If blocks that have already been visited are freed and new blocks are > allocated, the seen:allocated ratio is no longer an accurate estimate > of how much more work is needed to complete the scrub. > > Before the scrub prefetch code went in, I would routinely see scrubs > last 75 hours which had claimed to be "100.00% done" for over a day. >Arse, thanks Bill. I just stopped and restarted the scrub! -- Ian.
On Wed, Mar 17, 2010 at 7:09 PM, Bill Sommerfeld <sommerfeld at sun.com> wrote:> On 03/17/10 14:03, Ian Collins wrote: > >> I ran a scrub on a Solaris 10 update 8 system yesterday and it is 100% >> done, but not complete: >> >> scrub: scrub in progress for 23h57m, 100.00% done, 0h0m to go >> > > Don''t panic. If "zpool iostat" still shows active reads from all disks in > the pool, just step back and let it do its thing until it says the scrub is > complete. > > There''s a bug open on this: > > 6899970 scrub/resilver percent complete reporting in zpool status can be > overly optimistic > > scrub/resilver progress reporting compares the number of blocks read so far > to the number of blocks currently allocated in the pool. > > If blocks that have already been visited are freed and new blocks are > allocated, the seen:allocated ratio is no longer an accurate estimate of how > much more work is needed to complete the scrub. > > Before the scrub prefetch code went in, I would routinely see scrubs last > 75 hours which had claimed to be "100.00% done" for over a day.I''ve routinely seen that happen with resilvers on builds 126/127 on raidz/raidz2. It reaches completion and stay in progress for as much as 50 hours at times. We just wait and let it do its work. The bugs database doesn''t show if developers have added comments about that. Would have access to check if resilvers were mentioned ? BTW, since this bug only exists in the bug database, does it mean it was filled by a Sun engineer or a customer ? What''s the relationship between that and the defect database ? I''m still trying to understand the flow of information here, since both databases seem to be used exclusively for OpenSolaris but one is less open. -- Giovanni -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100317/529b0538/attachment.html>
On 03/18/10 11:09 AM, Bill Sommerfeld wrote:> On 03/17/10 14:03, Ian Collins wrote: >> I ran a scrub on a Solaris 10 update 8 system yesterday and it is 100% >> done, but not complete: >> >> scrub: scrub in progress for 23h57m, 100.00% done, 0h0m to go > If blocks that have already been visited are freed and new blocks are > allocated, the seen:allocated ratio is no longer an accurate estimate > of how much more work is needed to complete the scrub. > > Before the scrub prefetch code went in, I would routinely see scrubs > last 75 hours which had claimed to be "100.00% done" for over a day. >Interesting comparison, yesterday''s scrub counted down from about 25 hours to go, today''s is reporting: scrub: scrub in progress for 7h36m, 15.86% done, 40h22m to go Not much has changed in the pool over night. -- Ian.