Date: Fri, 13 May 2016 16:28:31 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-fs@freebsd.org Subject: Re: ZFS/Duplicated ZAP? Message-ID: <d66259e5-2349-210b-04a3-42b1564748e3@freebsd.org> In-Reply-To: <21a44c938d0f09c22ec5fe2a6d7d5013@thebighonker.lerctr.org> References: <0df84959a28476a61654a9d4893f3f11@thebighonker.lerctr.org> <2f38a63e226d1f88f68af69725111b85@thebighonker.lerctr.org> <21a44c938d0f09c22ec5fe2a6d7d5013@thebighonker.lerctr.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --BE8Wgxw7gJr81tetaxvqGVXNUa8RWCS41 Content-Type: multipart/mixed; boundary="1VCT3GEom1vGG6csPna5CA3gHWdTvCgm8" From: Matthew Seaman <matthew@freebsd.org> To: freebsd-fs@freebsd.org Message-ID: <d66259e5-2349-210b-04a3-42b1564748e3@freebsd.org> Subject: Re: ZFS/Duplicated ZAP? References: <0df84959a28476a61654a9d4893f3f11@thebighonker.lerctr.org> <2f38a63e226d1f88f68af69725111b85@thebighonker.lerctr.org> <21a44c938d0f09c22ec5fe2a6d7d5013@thebighonker.lerctr.org> In-Reply-To: <21a44c938d0f09c22ec5fe2a6d7d5013@thebighonker.lerctr.org> --1VCT3GEom1vGG6csPna5CA3gHWdTvCgm8 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 05/13/16 16:19, Larry Rosenman wrote: > Anyone? >=20 > On 2016-05-11 15:31, Larry Rosenman wrote: >> On 2016-05-11 15:23, Larry Rosenman wrote: >>> What can I do to fix these? A scrub does not. From looking at >>> comments where this is >>> generated, seems like it maybe dedupe related. Rebuilding the pool i= s >>> NOT an option at present. >>> >>> thebighonker.lerctr.org /home/ler $ grep -i zfs /var/log/messages >>> May 11 00:03:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entr= y >>> detected (libssl.a). >>> May 11 00:03:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entr= y >>> detected (libzpool.so). >>> May 11 00:03:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entr= y >>> detected (libtinfo_p.a). >>> May 11 00:03:31 thebighonker kernel: ZFS WARNING: Duplicated ZAP entr= y >>> detected (libumem.so). You could try doing a zfs send ... | zfs recv ... to create a new copy of the affected ZFSes. This should pretty much unwind any effect of having had deduplication turned on. Then it's a matter of using 'zfs rename' to move the new copy into the expected locations in your zfs hierarchy and have them mount at the correct places in your filesystem. That's something you'll almost certainly need to do while booted from a live CD or similar. Cheers, Matthew --1VCT3GEom1vGG6csPna5CA3gHWdTvCgm8-- --BE8Wgxw7gJr81tetaxvqGVXNUa8RWCS41 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJXNfKgAAoJEABRPxDgqeTnX7wQAKXtpw/m1qH8WDwf11NzSXYY KbCmK+eXjDTMsXmLvF+xXIy04D8ofNlaTTwhXU//xi8nDkGXeFD8087KMn9stQ7u RtS5INpm5PXh4HDrZlhlwmVmtju59W8T+brcwF/RzEHlB02Z0XgQe/4gBPiQtVRy fEYjtYv1oYSwxz/etRszBVHImpPSXavMswfABJi7smvPWJ7hXkLeLAhE3BrhWvzk IqGGy0S0qkL39Zp2o98K2vVdIY7Sy3+U+Zug4Cb1pxN2eJGbmTPPREC+5jcCsZ5P +/eWx+x2j5vVxCsudy7WcZtPjv6jUyguxVGgZ8fPCxEPFjhUtl2YZJu0UMOvrVso MQW/MQQoIVyZ1gI6IEQCtfQCoijXsIRRqy1rQ4xrrwWbD2bjSbJONg9CiXOAEQpY yLXDq39EqmKdrFTAxErwzG4s7xBWX3uGLp6sSmUDjPE1pPNgRpTsfeFjGHnxhT53 yGrucq1doYL+2xHfBi9soR/W1NYlOK2xIFPR1KI3yGGsyiVDnGpWk46HmjqboLnt SKjuBxHIvLSFoApAYqEEEmPoiGmjOkkzMgTZQEtP/hCo+KMviMg25yejDfgvtMks 4ESrfF3CKbEYy48VbEFX3k7qFDIBNfoYJUEXz8HLv1Yz4TdTwcPZ8qeOXJgfiMRY fBnKt3HoZzKUrcC2f5BY =LnbW -----END PGP SIGNATURE----- --BE8Wgxw7gJr81tetaxvqGVXNUa8RWCS41--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d66259e5-2349-210b-04a3-42b1564748e3>