From nobody Sun Oct 16 18:37:43 2022 X-Original-To: freebsd-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 4Mr8506Rytz4fp5h for ; Sun, 16 Oct 2022 18:37:56 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-vs1-f48.google.com (mail-vs1-f48.google.com [209.85.217.48]) (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 4Mr84z4xQxz42Fy for ; Sun, 16 Oct 2022 18:37:55 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-vs1-f48.google.com with SMTP id k6so9587710vsc.8 for ; Sun, 16 Oct 2022 11:37:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=qlPG0hIikdsTtosgPST7nOKf44WcXdZB/kYdKyoRN9U=; b=3avEqOnE8vqp3xHpp7SjKb71q2yr4p+ik136jdabevoVW/8oEOvlMiSTJCkS7LLiev xq4VlC2B/qkRPWstnKwfrCWUA8ySjbvxFm4NxlVfQPbvTQ4YBSUzUmYa8SrsxYQXhsH7 rDL7B19Xs0tx63Tpp+LrL2X0eLOyQY2KdVYTd/uJLc6GdN7RkG7qfvOseNLo82ePk031 1mQYJQeuzHtqgoSPonvUYZKHdAwA/3hsqHWngUaCYtfS/8A9Ge33W0AW/ahH4kSeNVg3 0lsBt6vcruthltdjeIQWKExVCCFouDUmLQyGcGZFafg04H/GhRkr3tA4uY9bpT17Cx1Q Dulg== X-Gm-Message-State: ACrzQf2jGr+7w08TCfnuWhQMIlEFohc/ua/cO0x+o3+h1Rjpmm+o5cNm zwdm2Uqmcsw4/UADOH4KWxRrSV+rVAwAwKvJlFRLy2rYsIg= X-Google-Smtp-Source: AMsMyM5oCVNwM90O4SVOv+Z3/ZafBWezDBG2iXb9VRftX5Y53vko1iOf4MYxB9F/lz3CJep28tmCVSWdJtEguz1F8bk= X-Received: by 2002:a05:6102:2908:b0:3a9:43be:5e44 with SMTP id cz8-20020a056102290800b003a943be5e44mr2764297vsb.74.1665945474991; Sun, 16 Oct 2022 11:37:54 -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: In-Reply-To: From: Alan Somers Date: Sun, 16 Oct 2022 12:37:43 -0600 Message-ID: Subject: Re: zfs with operations like rm -rf takes a very long time recently To: void Cc: freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4Mr84z4xQxz42Fy 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.217.48 as permitted sender) smtp.mailfrom=asomers@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; 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]; FREEMAIL_TO(0.00)[f-m.fm]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.217.48:from]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; 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.217.48:from]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; TO_DN_SOME(0.00)[]; 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)[freebsd-fs@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N On Sun, Oct 16, 2022 at 7:57 AM void wrote: > > Has anything recently changed in -current that would make file operations > on zfs such as rm -rf *.* very slow? > > What would I look for and how would I test it? > > system is FreeBSD 14.0-CURRENT #5 main-n258595-226e41467ee1 on arm64.aarch64 > using GENERIC-NODEBUG kernel. > > the zfs is zroot on usb3 on a raspberry pi4 8GB. there appears to be plenty > of resources. cpu speed is 2.1GHz. zroot is external usb3 hd. > > Right now it's rm -rf-ing /var/cache/ccache/* which is 5GB max and it's taken > over 10 mins. It was never this slow. No errors in /var/log/messages and none > yet in smartd. zpool scrub last ran successfully 3 days ago. Do you mean that the space used by that directory is 5 GB max? Or do you mean that you have a /var/cache dataset with a 5GB quota? In the latter case, if the usage is close to quota, then ZFS can slow down just as if the pool itself were nearly full. -Alan