Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 07 Mar 2020 18:29:15 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 244656] ZFS resilver in progress but which disks? And no progress?
Message-ID:  <bug-244656-227-FlzRpQpRYS@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-244656-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-244656-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D244656

--- Comment #1 from Peter Eriksson <pen@lysator.liu.se> ---
Oh, after many hours it seems to have finished:

# zpool status DATA2
  pool: DATA2
 state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
        still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not supp=
ort
        the features. See zpool-features(7) for details.
  scan: resilvered 152K in 0 days 06:07:55 with 0 errors on Sat Mar  7 19:2=
0:01
2020
config:
..
          diskid/DISK-7PH8GJTG    AVAIL=20=20=20

errors: No known data errors

(The reason it didn't have all features enabled was that I upgraded this se=
rver
from 11.3-p6 till 12.1-p2 as one of way to try to fix the problem...


# zpool list
NAME    SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAG    CAP  DEDUP  HEALTH
ALTROOT
DATA2   435T   390T  44.8T        -         -    23%    89%  1.00x  ONLINE =
 -
DATA3   145T  75.5T  69.5T        -         -    11%    52%  1.00x  ONLINE =
 -
zroot   113G  35.5G  77.5G        -         -    56%    31%  1.00x  ONLINE =
 -


and now zfs commands don't hang any more...

Now, a wild guess is that it was busy destroying defered-destroyed snapshot=
s.=20

Since before I restarted this server we had many thousands of those "delete=
d"
with "zfs destroy -d FS@SNAPSHOT". Hmm.. I wonder if it would be possible to
make this more visible somehow - perhaps a "destroyed-snapshots" counter vi=
a a
sysctl or something? And/or have some way to pause the snapshot-deletion th=
read
(similar to "zfs scrub -p").

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-244656-227-FlzRpQpRYS>