From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6855AC77B73 for ; Wed, 31 May 2023 14:27:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236497AbjEaO1T (ORCPT ); Wed, 31 May 2023 10:27:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41506 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236413AbjEaO1N (ORCPT ); Wed, 31 May 2023 10:27:13 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DCD5E197 for ; Wed, 31 May 2023 07:27:05 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id C63DA68B05; Wed, 31 May 2023 16:17:39 +0200 (CEST) Date: Wed, 31 May 2023 16:17:39 +0200 From: Christoph Hellwig To: Johannes Thumshirn Cc: Christoph Hellwig , Qu Wenruo , Naohiro Aota , "linux-btrfs@vger.kernel.org" Subject: Re: new scrub code vs zoned file systems Message-ID: <20230531141739.GA2160@lst.de> References: <20230531125224.GB27468@lst.de> <546fad79-f436-c561-8b9b-0d9a7db09522@wdc.com> <20230531132032.GA30016@lst.de> <821003e3-b457-90ba-e733-8c2fdd0c3b3c@wdc.com> <20230531133038.GA30855@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org On Wed, May 31, 2023 at 02:04:05PM +0000, Johannes Thumshirn wrote: > > Heh and this has never actually worked IMHO. > > I did a crude hack to bandaid scrub: I think the better approach is to: a) branch out at a very high level to the zoned code in flush_scrub_stripes, or in fact even higher given that we don't really care about tracking stripes. The write side of scrub has to work at a zone, not stripe level for zoned devices b) don't create a new relocation thread per zone, but run it from the scrub context.