Date: Wed, 07 Jun 2017 18:21:09 +1000 From: Stephen McKay <mckay@FreeBSD.org> To: =?UTF-8?Q?=c5=81ukasz_W=c4=85sikowski?= <lukasz@wasikowski.net> Cc: freebsd-fs@freebsd.org, mckay@FreeBSD.org Subject: Re: Problem with zpool remove of log device Message-ID: <0410af$1dldvp4@ipmail04.adl6.internode.on.net> In-Reply-To: <9188a169-cd81-f64d-6b9e-0e3c6b4af1bb@wasikowski.net> from =?UTF-8?Q?=c5=81ukasz_W=c4=85sikowski?= at "Fri, 26 May 2017 11:40:06 %2B0200" References: <9188a169-cd81-f64d-6b9e-0e3c6b4af1bb@wasikowski.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, 26th May 2017, lukasz@wasikowski.net wrote: >I cant remove log device from pool - operation ends ok, but log device >is still in the pool (bug?). > ># uname -a >FreeBSD xxx.yyy.com 11.0-STABLE FreeBSD 11.0-STABLE #0 r316543: Thu Apr >6 08:22:43 CEST 2017 root@xxx.yyy.com:/usr/obj/usr/src/sys/YYY amd64 > ># zpool status tank >[..snip..] > > NAME STATE READ WRITE CKSUM > tank ONLINE 0 0 0 > mirror-0 ONLINE 0 0 0 > ada2p3 ONLINE 0 0 0 > ada3p3 ONLINE 0 0 0 > logs > mirror-1 ONLINE 0 0 0 > gpt/tankssdzil0 ONLINE 0 0 0 block size: 512B configured, 4096B native > gpt/tankssdzil1 ONLINE 0 0 0 block size: 512B configured, 4096B native >When I try to remove log device operation ends without errors: > ># zpool remove tank mirror-1; echo $? >0 > >But the log device is still there: >[..snip..] >I'd like to remove it - how should I proceed? Does your system still write to the log? Use "zfs iostat -v 1" to check. I think it is probably no longer be in use and only the final disconnection failed. What does "zpool list -v" tell you? If you have a non-zero ALLOC column for your log mirror and the log is no longer being used then you may have hit an accounting bug in zfs that the zfsonlinux people ran into a while ago. I had this problem when I tried to remove a log mirror from a pool I have been using for years. I solved it by tweaking the zfsonlinux hack a bit and slotting it into 9.3. If you apply this hack be sure to have a full backup first! When I used it, I did my backup and a scrub then booted the hacked kernel, issued the zfs remove command (which succeeded), reverted the kernel, then scrubbed again. All went well. Good luck! Here's the patch against 9.3 (should be close even for 11.0): Index: sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c =================================================================== --- sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c (revision 309860) +++ sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c (working copy) @@ -5446,6 +5446,18 @@ ASSERT(vd == vd->vdev_top); /* + * slog stuck hack - barnes333@gmail.com + * https://github.com/zfsonlinux/zfs/issues/1422 + */ + if (vd->vdev_islog && vd->vdev_removing + && vd->vdev_state == VDEV_STATE_OFFLINE + && vd->vdev_stat.vs_alloc > 0) { + printf("ZFS: slog stuck hack - clearing vs_alloc: %llu\n", + (unsigned long long)vd->vdev_stat.vs_alloc); + vd->vdev_stat.vs_alloc = 0; + } + + /* * Only remove any devices which are empty. */ if (vd->vdev_stat.vs_alloc != 0) Cheers, Stephen.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0410af$1dldvp4>