Date: Fri, 15 Jul 2022 10:49:10 -0500 From: "Zane C. B-H" <v.velox@vvelox.net> To: Alan Somers <asomers@freebsd.org> Cc: freebsd-fs <fs@freebsd.org> Subject: Re: ZFS dataset stats Message-ID: <a17295f44e368d716c79b331afd3d5a7@vvelox.net> In-Reply-To: <CAOtMX2gT041Wp9Vm_Mm=KTEAn=RFta5vpDPpFEUTYNaRXpdu3w@mail.gmail.com> References: <42b403fd492b631ad14e97b7e8a9778f@vvelox.net> <CAOtMX2gT041Wp9Vm_Mm=KTEAn=RFta5vpDPpFEUTYNaRXpdu3w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
ZFS with the volmode set to dev being used by bhyve on FreeBSD stable/12-n234444-680eb3fd094. /usr/bin/lockf -s -t0 /storage/cbsd/tmp/bhyveload.debian10_test.lock env LIB9P_LOGGING=/storage/cbsd/jails-system/debian10_test/cbsd_lib9p.log /usr/bin/nice -n 1 /usr/sbin/bhyve -c 1 -m 4294967296 -H -A -U 2bc5ac97-8438-11ec-a89a-90b11c06ff98 -s 0,hostbridge -s 1,ahci-cd,/usr/local/cbsd/upgrade/patch/efirefd.fd,ro -s 4,virtio-blk,/storage/cbsd/vm/debian10_test/dsk1.vhd,sectorsize=512/4096 -s 5,virtio-net,tap9,mac=00:a0:98:5c:63:1f -s 6,virtio-rnd -s 8,fbuf,tcp=127.0.0.1:5909,w=1024,h=768,password=cbsd -s 30,xhci,tablet -s 31,lpc '/storage/cbsd/vm/debian10_test/dsk1.vhd' is just a symlink to '/dev/zvol/storage/debian10_test/dsk1.vhd'. And ztop also fails here as well. On 2022-07-15 07:59, Alan Somers wrote: > 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 <v.velox@vvelox.net> > 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? >>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a17295f44e368d716c79b331afd3d5a7>