From nobody Mon Dec 13 07:30:50 2021 X-Original-To: freebsd-current@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 7B77118D5388 for ; Mon, 13 Dec 2021 07:30:53 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4JCCq12Nyxz3PV9; Mon, 13 Dec 2021 07:30:53 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from [192.168.0.88] (unknown [195.64.148.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: avg/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id B65CA24009; Mon, 13 Dec 2021 07:30:52 +0000 (UTC) (envelope-from avg@FreeBSD.org) Message-ID: Date: Mon, 13 Dec 2021 09:30:50 +0200 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Firefox/91.0 Thunderbird/91.4.0 Subject: Re: CURRENT: ZFS freezes system beyond reboot Content-Language: en-US To: Alan Somers , FreeBSD User Cc: FreeBSD CURRENT References: <20211212102032.08af9689@jelly.fritz.box> From: Andriy Gapon In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1639380653; 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=izlf0xYrKuJcX2O3IUEaXwLWl7yTzGTyP9nlvPo1hLY=; b=gg11E56p+XNLDNhByCgU5QYIQX8qpTKsXpQ18HNPW7hKvwkjr6c4VZWFEZ5lUkQrMs/ZZL SonDq/1UT6BpjOIA2Nmb4FI1b8jXipNZly/O78MfjiZ3QrOBaoDRWUyVK0JDxYR+IF1mtY UgWU/ZUwEK3/5gbDbibLB6TvN4b59HI4pAAMNuJLeC00VoSDfzU1otEBP+NPRTDq34vit2 cpnEu8+HznnRDS8FqnQGCPBoesvqonO4WDu9+7+xTiuz6pb4zJog1H8WCBSbAUGAmbN+hX s37r6bl3Ez1jevrA0NtBmLRneea6e/MFR25bdDc0wi6JgVgH3SOhdV/3nfYVxw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1639380653; a=rsa-sha256; cv=none; b=bsgetSiEGm/tG5tv+uJ0Fd+nRPJgIlST8X0rm8rgMbqfuQadMPIcDjjND5nRT4PRXmSnUx stFn7PZEzga9fHdo4LyTMtZFZ5RckR9wrc65MJEzVasz0fNAg3Bb++FNEYoNTyl5/5TNda yB7JqJSBoXEn3jokhgZVgX8dBFX/gexdBRtwUjMBCwyrvqDrrxy/9oKW46OaKMWCuMdski X3kBLao42FnzFfSENo3XcaPGhzghYFS66aJgFL1F3SCKmkB2P4/TEGXnDATLkubzlYLHTP jMHnW9SNPQsM2J+QvGIT5umgCIL+zWq8qiCtvEfqjw5sl8BkJ5J5v33X02b1pA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On 12/12/2021 18:45, Alan Somers wrote: > You need to look at what's causing those errors. What kind of disks > are you using, with what HBA? It's not surprising that any access to > ZFS hangs; that's what it's designed to do when a pool is suspended. However, a pool does not have to be suspended on errors. failmode property provides a couple of alternatives: wait Blocks all I/O access until the device connectivity is recovered and the errors are cleared. This is the default behavior. continue Returns EIO to any new write I/O requests but allows reads to any of the remaining healthy devices. Any write requests that have yet to be committed to disk would be blocked. panic Prints out a message to the console and generates a system crash dump. But neither does any magic. The errors will still be there. -- Andriy Gapon