From owner-freebsd-questions@freebsd.org Mon Apr 29 10:03:36 2019 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DBA311586BED for ; Mon, 29 Apr 2019 10:03:35 +0000 (UTC) (envelope-from bblister@gmail.com) Received: from n6.nabble.com (n6.nabble.com [162.255.23.37]) by mx1.freebsd.org (Postfix) with ESMTP id 582546E0E3 for ; Mon, 29 Apr 2019 10:03:34 +0000 (UTC) (envelope-from bblister@gmail.com) Received: from n6.nabble.com (localhost [127.0.0.1]) by n6.nabble.com (Postfix) with ESMTP id 31A47DF4E7C8 for ; Mon, 29 Apr 2019 03:03:27 -0700 (MST) Date: Mon, 29 Apr 2019 03:03:27 -0700 (MST) From: BBlister To: freebsd-questions@freebsd.org Message-ID: <1556532207201-0.post@n6.nabble.com> Subject: zfs reports: "bad property list: invalid property 'checkpoint'" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 582546E0E3 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dmarc=fail reason="" header.from=gmail.com (policy=none); spf=softfail (mx1.freebsd.org: 162.255.23.37 is neither permitted nor denied by domain of bblister@gmail.com) smtp.mailfrom=bblister@gmail.com X-Spamd-Result: default: False [-1.84 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.91)[-0.908,0]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; TO_DN_NONE(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.96)[-0.964,0]; IP_SCORE(0.07)[ip: (0.29), ipnet: 162.255.20.0/22(0.08), asn: 21624(0.04), country: US(-0.06)]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.13)[-0.133,0]; RCVD_IN_DNSWL_NONE(0.00)[37.23.255.162.list.dnswl.org : 127.0.10.0]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:21624, ipnet:162.255.20.0/22, country:US]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Apr 2019 10:03:36 -0000 On my FreeBSD XXXX 11.2-RELEASE-p9 FreeBSD 11.2-RELEASE-p9 #0: Tue Feb 5 15:30:36 UTC 2019 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 every time I issue zpool list the following error is emitted as you can see bellow. According to #zpool history this pool was created on FreeBSD on 2010-08-18.18 and has been running on the same disk flawlessly 24/7 even though M/B and cpu were occasionally upgraded. The tool is operational and is heavily used. It is not a boot ZFS pool. Just a storage area. zfs scrub reports no problems. This pool was always connected to the FreeBSD and never to a Linux or other OS. I have been always doing a freebsd-update and zpool upgrade after every major FreeBSD version upgrade. I am not sure why this has happened. I just noticed one day. I cannot export/import this pool because this is on a remote server and I fear that i may not be able to re-import it again. According to zfs history the last upgrade was: ... 2017-02-05.12:19:35 zpool upgrade tank .... after this there are zpool scrub tank entries. The uptime is 76 days and I would not like to perform a reboot because it may cause the pool not to be mounted. I would like to fix it without reboot. The questions are: 1) Is the property 'checkpoint' supported on 11.2-RELEASE-p9 2) How can I remove this property and all the (null) properties as reported by zpool upgrade. Thank you very much for your help. Any suggestions are welcome. ================================= # zpool list bad property list: invalid property 'checkpoint' usage: list [-Hpv] [-o property[,...]] [-T d|u] [pool] ... [interval [count]] the following properties are supported: PROPERTY EDIT VALUES allocated NO capacity NO dedupratio NO <1.00x or higher if deduped> expandsize NO fragmentation NO free NO freeing NO guid NO health NO leaked NO size NO altroot YES autoexpand YES on | off autoreplace YES on | off bootfs YES cachefile YES | none comment YES dedupditto YES delegation YES on | off failmode YES wait | continue | panic listsnapshots YES on | off readonly YES on | off version YES feature@... YES disabled | enabled | active The feature@ properties must be appended with a feature name. See zpool-features(7). Also zpool-upgrade does not operate: ================================= # zpool upgrade This system supports ZFS pool feature flags. All pools are formatted using feature flags. Some supported features are not enabled on the following pools. Once a feature is enabled the pool may become incompatible with software that does not support the feature. See zpool-features(7) for details. POOL FEATURE --------------- tank (null) (null) (null) # zpool upgrade -a This system supports ZFS pool feature flags. cannot set property for 'tank': invalid feature '(null)' ================================= -- Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-questions-f3696945.html