From nobody Thu Dec 14 22:10:30 2023 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 4Srmkd2rFbz53qdx for ; Thu, 14 Dec 2023 22:10:33 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [66.165.241.226]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Srmkd0vVZz4vbP for ; Thu, 14 Dec 2023 22:10:33 +0000 (UTC) (envelope-from pete@nomadlogic.org) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomadlogic.org; s=04242021; t=1702591831; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=R/nUn1kmCE2/Z8udTAKslpnpW0dz/PlXrweijvYdX5I=; b=FcqEJeRFNJDIS823jJ1d1H+WFh64cNDmop07c+Zh37CVeuvasRf32d8whZy394GVmy6l+v tOMY6ptk61lomUCuC8GRfjhKO2K+JoXfWWtreJVAK8JuHLbS2tYBrJKGqHBmqb/tIL+aCH kPzw6fbblMVrW7s2pE0MBmcEW9SJqZE= Received: from [192.168.1.240] (024-024-168-214.inf.spectrum.com [24.24.168.214]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 39377143 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Thu, 14 Dec 2023 22:10:31 +0000 (UTC) Message-ID: Date: Thu, 14 Dec 2023 14:10:30 -0800 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 User-Agent: Mozilla Thunderbird Subject: Re: unusual ZFS issue Content-Language: en-US To: Lexi Winter Cc: "freebsd-fs@freebsd.org" References: <787CB64A-1687-49C3-9063-2CE3B6F957EF@le-fay.org> From: Pete Wright In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:29802, ipnet:66.165.240.0/22, country:US] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4Srmkd0vVZz4vbP On 12/14/23 2:05 PM, Lexi Winter wrote: > On 14 Dec 2023, at 22:02, Pete Wright wrote: >> On Thu, Dec 14, 2023 at 09:17:06PM +0000, Lexi Winter wrote: >>> hi list, >>> >>> i’ve just hit this ZFS error: >>> >>> # zfs list -rt snapshot data/vm/media/disk1 >>> cannot iterate filesystems: I/O error >> >> hrm, i wonder if you see any errors in dmesg or /var/log/messages about a >> device failing? > > nothing that looks relevant in the last few days (the problem appeared last night, Dec 13th): > > Dec 11 15:44:21 hemlock kernel: ix1: link state changed to DOWN > Dec 11 15:44:21 hemlock kernel: ix1.107: link state changed to DOWN > Dec 11 15:44:35 hemlock kernel: ix1: link state changed to UP > Dec 11 15:44:35 hemlock kernel: ix1.107: link state changed to UP > Dec 11 15:44:47 hemlock kernel: nfsrv_cache_session: no session IPaddr=2001:8b0:aab5:ffff::2, check NFS clients for unique /etc/hostid's > Dec 11 15:44:47 hemlock syslogd: last message repeated 1 times > Dec 11 17:00:48 hemlock kernel: tcp_vnet_init: WARNING: unable to initialise TCP stats > Dec 11 17:00:48 hemlock kernel: lo0: link state changed to UP > Dec 12 06:17:23 hemlock ntpd[25836]: leapsecond file ('/var/db/ntpd.leap-seconds.list'): will expire in less than 16 days > Dec 13 06:17:23 hemlock ntpd[25836]: leapsecond file ('/var/db/ntpd.leap-seconds.list'): will expire in less than 15 days > Dec 14 06:17:23 hemlock ntpd[25836]: leapsecond file ('/var/db/ntpd.leap-seconds.list'): will expire in less than 14 days > Dec 14 16:30:12 hemlock smbd[98264]: [2023/12/14 16:30:12.404883, 0] ../../source3/smbd/server.c:1741(main) > Dec 14 16:30:12 hemlock smbd[98264]: smbd version 4.16.11 started. > Dec 14 16:30:12 hemlock smbd[98264]: Copyright Andrew Tridgell and the Samba Team 1992-2022 > > i’ve also checked the disks with smartctl and i didn’t see any errors there. (a couple of devices have corrected read errors, but that’s expected given their age - and if it *was* a disk error i’d expect it to show up as a checksum error). > dang, was hoping something obvious would pop up there or with smartctl. hopefully others here have some ideas about trying to find the root cause before a restart. -pete -- Pete Wright pete@nomadlogic.org