Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp1867676rwd; Mon, 15 May 2023 04:21:24 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4FtKdaHosh6GsHBEmAvezTObyy20pIhOpFmXFx2oAf7vNivzM6Je+2egihIti1aX47F8+C X-Received: by 2002:a05:6a20:440a:b0:101:6a81:619f with SMTP id ce10-20020a056a20440a00b001016a81619fmr26310417pzb.39.1684149684154; Mon, 15 May 2023 04:21:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1684149684; cv=none; d=google.com; s=arc-20160816; b=sYxKI3qG3V+QaPKs0dvaBkJ8c8ew+PSOFQrfWZl/vf5TnhW2eHDlHnKjNyygIhrsRF 0JvGHHFbCzUzEGZKtzMUOOoBMqFH4/YP8kCjwwI7WcqwLLVGtHgMVoQ9CwAFNIvyELew SdMBnladn5BsxQXA0X/arqGiiv0hr2Mq2Fm5BWwCbzH9I7g6nCdl7Je4o47+hEDh0AU1 oMi1n13hcFV4pOYO3ahfwik6DkdWFoCA9VULn9ecOFclY8T9Mhi1VIHr6DzPyP5dnKvj gElmeRnggldWEVFcZ1pBduiv2snyDGMPL+X7UPQmlPuIiYfNvA1TCTkOlI2+Qlw+8kMH zf7Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:mime-version:dkim-signature; bh=TTbXuYdaoyxAlzcRp/fw5Y/X7Jv1gcBGl293JJcjEdw=; b=m2pNyV8RSdBTif9cV6c/1E+1eXFP8jpskgicA1V/hMVMoWscJPSZazWQGLM36rR9nB ebDjG9pshH6N9CZ7dgE6wJWhlmnRBS5FII1VJG1K5VmkobjMDtpelgVue0HtRtKJekRT v8EhubAUsQzhhQAFuiw4m9dheTEzkSI9wvnCYb1soAUDfvJI+PRTSyX/Wkdf+JnnCzvy D+XvfyYLyZSwRqjPIt8jOroJ/XyBtx9d7OikPfBHnlFkXrgbFoBlFMJT6XYIl/2vzPus U2hmuVf1OBqCZOsuGyIJv/1pcWyTPPJvbROWoHVjOUTUQzPfM7n8eHAGxqceBgRaVuXq SbHg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20221208 header.b=rHvms3r0; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id o10-20020a637e4a000000b00524b3efc310si15349182pgn.83.2023.05.15.04.21.11; Mon, 15 May 2023 04:21:24 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20221208 header.b=rHvms3r0; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241215AbjEOLQd (ORCPT + 99 others); Mon, 15 May 2023 07:16:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56872 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240360AbjEOLQ1 (ORCPT ); Mon, 15 May 2023 07:16:27 -0400 Received: from mail-yb1-xb36.google.com (mail-yb1-xb36.google.com [IPv6:2607:f8b0:4864:20::b36]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 92B74172B; Mon, 15 May 2023 04:16:26 -0700 (PDT) Received: by mail-yb1-xb36.google.com with SMTP id 3f1490d57ef6-ba7831cc80bso346576276.0; Mon, 15 May 2023 04:16:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684149386; x=1686741386; h=content-transfer-encoding:cc:to:subject:message-id:date:from :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=TTbXuYdaoyxAlzcRp/fw5Y/X7Jv1gcBGl293JJcjEdw=; b=rHvms3r0j62HT8lJLCgjCOTVIvfLAuQQowXP8AlPbnL6ZdyWDLMK5IwWZH9as9mBWi pq0PzbvF/mx+rD6DVkQk3fjS477v0OxylXei5cwqQcrzF8gRJiH0GlT4Oox8bYu4GLrB N3+IOgs3o+BqCPUHE9+VAav5BHIGiuKOk3gVX3b1Sfk0yf1BB2u6uiqw2mcyKGd/x1gf xmnyc09sWRSVZoXzSO30cCgzd3imc9NVHznBTuiVFfgJiA12Uh9fMx/gmMffJxzsyDUO RcNyG5WSoSePuBrPVRq1oc/kE2nN0ByBIfb7qGJnsOvLNqlRgyzQnmZCDAkx4wu8gR6a 6F2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684149386; x=1686741386; h=content-transfer-encoding:cc:to:subject:message-id:date:from :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=TTbXuYdaoyxAlzcRp/fw5Y/X7Jv1gcBGl293JJcjEdw=; b=kWDSnbAcyt3iri41976YRRISaim0kKezz0lm012bIeNvZfN5WuMYUi5qSqgG6y0Vlf czQ/1OjlVmUgJoLOczP3CZpH66/sliGFdLSpZYZlbf/r0ANFzpPubtRXo60AUQ9rYOci 6GMGd0DuI34q3AAm4E7gb3tCNjONUNG+2PyFHA7J0BGSM1z/+RFHMBok+73Ybpm7Yont Zf4BO9GXwF3lmw/G6QKw9hxrRQVweC0DKzIIb/PnQiOTGXSGGRDE0f9YBmPEhXgQt+2Y FCQ3m2bYbsGliabGHsFXijE25zkrhLxEOigUZtIWXZlk+dPTQyUsVIcpoYALv+sqv2xj nLCw== X-Gm-Message-State: AC+VfDxH6NsCAolASxyKCaBzgLQinQeltuIBqc2UudF6tndableCc7pe ZIOjRBk92wXtxnYPjlDDRsjsLy9ivPlBvP8empY= X-Received: by 2002:a81:1b4e:0:b0:55a:1cdc:2ed3 with SMTP id b75-20020a811b4e000000b0055a1cdc2ed3mr19282070ywb.2.1684149385714; Mon, 15 May 2023 04:16:25 -0700 (PDT) MIME-Version: 1.0 From: Askar Safin Date: Mon, 15 May 2023 14:15:48 +0300 Message-ID: Subject: Re: [PATCH 00/32] bcachefs - a new COW filesystem To: Kent Overstreet Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org, linux-mm@kvack.org, linux-bcachefs@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=0.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,SUSPICIOUS_RECIPS, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Kent, please, make sure you dealt with problems specific to another fs: btrfs: https://arstechnica.com/gadgets/2021/09/examining-btrfs-linuxs-p= erpetually-half-finished-filesystem/ . In particular, I dislike this btrfs problems, mentioned in the article: - "Yes, you read that correctly=E2=80=94you mount the array using the name = of any given disk in the array. No, it doesn't matter which one" - "Even though our array is technically "redundant," it refuses to mount with /dev/vdc missing... In the worst-case scenario=E2=80=94a root filesystem that itself is stored "redundantly" on btrfs-raid1 or btrfs-raid10=E2=80=94the entire system refuses to boot... If you're thinkin= g, "Well, the obvious step here is just to always mount degraded," the btrfs devs would like to have a word with you... If you lose a drive from a conventional RAID array, or an mdraid array, or a ZFS zpool, that array keeps on trucking without needing any special flags to mount it. If you then add the failed drive back to the array, your RAID manager will similarly automatically begin "resilvering" or "rebuilding" the array... That, unfortunately, is not the case with btrfs-native RAID" I suggest reading the article in full, at least from section "Btrfs RAID array management is a mess" till the end. Please, ensure that bcachefs has no these problems! These problems scary me away from btrfs. Please, CC me when answering --=20 Askar Safin