From nobody Fri Jul 15 12:59:06 2022 X-Original-To: fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4LkrzB5wGSz4Wbdf for ; Fri, 15 Jul 2022 12:59:18 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-qk1-f176.google.com (mail-qk1-f176.google.com [209.85.222.176]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Lkrz975W0z3qLh for ; Fri, 15 Jul 2022 12:59:17 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-qk1-f176.google.com with SMTP id h6so662897qkl.12 for ; Fri, 15 Jul 2022 05:59:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=nm8cLjEm8nMCDhpW/IK0qYvwr52Uka5cObYrZuEea3A=; b=n3f5VmGa08+fedXzH6TDHjpLzR5UGZk8i2SJgHNuAUcgScgIfETHJl7tkJFDcJliNh kWmisNeU9X1Pw4KUXa/7LNIoqYLlvih0Gwbo8fOYoTPZVEIdk5TRlL5nJeLm/lOxZ/Kf CHuFCuNor2Ff1EyqyNurI4QUb65MwS2NFdjKtkq4CbVNOpPWIq6nl9IwvCj8LeBQL0Rp xcz8yNFD1Uq41nESWiIPn+CBJkW0LFYyIjqGbe20es4ugITa6wGF5OQosr/5I46SGnJd MSDEJ0vVPGYQ+GRKYRjfEA9i8oAaSsbbupEccRlkE2l3dDs2dzCQKAVr36iqIXyljQyh nF/g== X-Gm-Message-State: AJIora8EEdvMOsaioNudBFUC+JPKZ/bUpB1L5KmnYnHM/cWx2270oWmd h28iI4pZleUdTc3N0eipt0dXWHKa9O1CzlYY2GLtn4T9 X-Google-Smtp-Source: AGRyM1teI/8HVPmCysZF4nb+o2KlUnonPYaQ3qwKhmrPpiN5A9Yo8nlqXlGp5BhtDFlJXm0WfpA+Dy4xPoSqhPeDMa8= X-Received: by 2002:a05:620a:102e:b0:6b5:c925:788d with SMTP id a14-20020a05620a102e00b006b5c925788dmr4023412qkk.517.1657889956916; Fri, 15 Jul 2022 05:59:16 -0700 (PDT) List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 References: <42b403fd492b631ad14e97b7e8a9778f@vvelox.net> In-Reply-To: <42b403fd492b631ad14e97b7e8a9778f@vvelox.net> From: Alan Somers Date: Fri, 15 Jul 2022 06:59:06 -0600 Message-ID: Subject: Re: ZFS dataset stats To: "Zane C. B-H" Cc: freebsd-fs Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4Lkrz975W0z3qLh X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.222.176 as permitted sender) smtp.mailfrom=asomers@gmail.com X-Spamd-Result: default: False [-2.99 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.987]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[fs]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.222.176:from]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; RCVD_IN_DNSWL_NONE(0.00)[209.85.222.176:from]; TO_DN_ALL(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[asomers]; RCPT_COUNT_TWO(0.00)[2]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[fs@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N You didn't say how you were accessing that dataset, or what FreeBSD version you're using. The dataset stats to update as expected in response to normal user I/O, but not zfs send/recv. Maybe there is another path that bypasses them too. How are you accessing them? BTW, sysutils/ztop from ports displays real-time measurements based on these stats. -Alan On Thu, Jul 14, 2022 at 11:05 PM Zane C. B-H wrote: > > So was just looking and for some reason nread etc for the ZFS storage > stats. > > Below is a example of a ZFS dataset being used by CBSD to store a raw > disk image, > one that is running currently, but for some reasonn the R/W stats don't > seem actually update. > > kstat.zfs.storage.dataset.objset-0x1d41.nread: 0 > kstat.zfs.storage.dataset.objset-0x1d41.reads: 0 > kstat.zfs.storage.dataset.objset-0x1d41.nwritten: 0 > kstat.zfs.storage.dataset.objset-0x1d41.writes: 0 > kstat.zfs.storage.dataset.objset-0x1d41.dataset_name: > storage/debian10_test/dsk1.vhd > > Is there any way to get ZFS to actually keep these up to date for use > cases > like this? >