Replaced old small drive with new one stuck resilvering

TrueNAS General
1

Used replace disk option in UI.
resilvering status is now over 200% and still climbing :exploding_head:
status scanning.
I did not pull old drive.
what i do. HELP

2

maybe gui bug? What’s the output of zpool status

3

Its shows over 100% why. there is disc activity. Data is being written to the new disc and read from the old one

root@truenas:/# zpool status
  pool: Main2.0
 state: ONLINE
status: One or more devices is currently being resilvered.  The pool will
        continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
  scan: resilver in progress since Fri Dec 27 13:03:49 2024
        7.20T / 6.53T scanned, 514G / 211G issued at 146M/s
        513G resilvered, 243.24% done, no estimated completion time
config:

        NAME                                        STATE     READ WRITE CKSUM
        Main2.0                                     ONLINE       0     0     0
          mirror-0                                  ONLINE       0     0     0
            e57094a7-8da4-40c9-a291-0b43ee7f8191    ONLINE       0     0     0
            a895d4dc-18d1-416b-a7a8-e6c75c114d10    ONLINE       0     0     0
          mirror-1                                  ONLINE       0     0     0
            64d9b129-d878-4993-b5a4-e4821b9324c3    ONLINE       0     0     0
            fedd7fd5-9f84-44b6-b68c-caf0e6ecc5ad    ONLINE       0     0     0
          mirror-2                                  ONLINE       0     0     0
            replacing-0                             ONLINE       0     0     0
              d43a9429-4b33-4a6f-a008-e2880233d4c5  ONLINE       0     0     0
              ab44f352-7c90-4e08-ad13-8949921843b2  ONLINE       0     0     0  (resilvering)
            41dc4a19-f3b0-4b02-8b8b-66dd81c81d1a    ONLINE       0     0     0
        logs
          mirror-3                                  ONLINE       0     0     0
            d1144ed9-7edc-41ec-9485-5d8a5bd2e927    ONLINE       0     0     0
            e2dfb37c-6355-43c1-a234-74f750d3de0b    ONLINE       0     0     0
        cache
          a2a2df64-9bea-4b5e-910f-817477e7f978      ONLINE       0     0     0

errors: No known data errors
4

ok it seems to have completed just fine. Yay I found a UI bug. still doesn’t explain why its showing over 100% on zpool status though.

1 Like
5

Without knowing anything in general - some googlefu implies that the % completion is generally a bad indicator & also that any writes that were done during the resilver process contributing further to the % completion being wrong.

So I guess if the pool was in use & actively doing the needful, the original amount of data that was expected to be resilvered was too small of an estimate vs the total that was actually done.

I found some folks questioning the same thing all the way back in early 2010s - I guess it is a ‘feature’ not a ‘bug’ at this point :smiley:

6

well ok cool non destructive bug. wow 2010 how has this not been fixed.

7

Eh I guess it only takes into account the original estimate of total data to be resilvered & then only updates how much data has been resilvered to calculate the % completed… but if it then processes more data than was initially estimated, then the % completed goes over 100.

I’m guessing no one wants to update the total data value to be dynamically adjusted during the process because then people can/will complain that “my resilver was at 95% done, and now it is 91% done!!11!1 Why is it going backwards?!”

8

Far point. Or they could freeze the progress bar. i mean over 100% makes less since than it going backwards. as you still end up with people very confused.

9

I would freak if I saw a resilver stuck at 100% but still ongoing, so I guess there really is no winning. LOL - I can see the ZFS patch notes now:

To reduce user confusion, we’ve removed completion estimates from all commands. This will ensure no errors in reporting.

It’s the only way to make everyone happy.

10

thanks for that. :rofl:

1 Like