From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wm1-f53.google.com (mail-wm1-f53.google.com [209.85.128.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B5668390C95 for ; Tue, 14 Apr 2026 12:11:57 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.128.53 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776168719; cv=none; b=I6yKcpcQ+Z3d/rMOSvy6mY9DNux//GNYN8qJWeJZ1fAwvy5oYuwBSZ4Cn7vNZYMt2h1qPrE2cTa7bIUJrRM6He6pxMbADCJPuKW4eXflvWx9jVjkJzCqhLAqLzPbaYM7Gh2hy6Nc7VRnku+bgWWI3BhAh2WU98NXObRmuUm+awE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776168719; c=relaxed/simple; bh=b79a/FeRzU7DAYcvsukbMcvTIdQXuX/Qu+vm+CTVtoI=; h=From:To:Cc:Subject:In-Reply-To:References:Content-Type:Date: Message-Id; b=M4VjGlAWmCsHIEhh20AUMdBu+HI0z4OoaHRjVfq+vcbYP5z1r9xY8aI8sBqkkxUJUw+LMmcOAczqMX8T8TQ6QNMaqZNZXeUbpunyh1RBt5bxqjuWXWHrSWOd39G2R3wgnMrqGAhUC6cJwri3H9SUxJsB+GpukhyvJrlCw0p1R24= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=hackers.camp; spf=pass smtp.mailfrom=gmail.com; arc=none smtp.client-ip=209.85.128.53 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=hackers.camp Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-wm1-f53.google.com with SMTP id 5b1f17b1804b1-488822b93c7so6120595e9.1 for ; Tue, 14 Apr 2026 05:11:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1776168716; x=1776773516; h=message-id:date:references:in-reply-to:subject:cc:to:from:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=b79a/FeRzU7DAYcvsukbMcvTIdQXuX/Qu+vm+CTVtoI=; b=JwjsLjfb7J3T6Gk08bqnrFBJ9pQ78Zhx6whAtVP61JA0zqHXuLckpEN4KV9n7gy/3N K1KSPWND8tlpXB2hkrTsm/JIlGkfaObp1IEIKiTTaaGdgFnBipYkVnU5xy/KgpxOafDb fUnh5gQQ9/tmGVIbwoSrfey8pIGdB/7PlB4a5Aeu3YK/VkXigaAwjxGPCqa/WFSq1ct2 CkPnyUEh9MxeGujWYIRTvCVt0mHGkGfKbO7CtWNhI96J5jfiOK6Jhmze1p/uKEH80Ytq TSi13Mc4OQBUX90wvcNlnZf9Dnr+6xYYqVgYu877TMa4TKoE1MC2Kd86HFGY2k4EQK/1 4jbw== X-Forwarded-Encrypted: i=1; AFNElJ8ZtA+Pc8SdTnc37R2zHajPHyocu24SLlLZiPrNX3IKxcJTR3R6Uta2CPc4AE8hwls27pib4F2hcw+p2VI=@vger.kernel.org X-Gm-Message-State: AOJu0YxX6ox4WcdZdaK4PZfG2amE8PahRntOjuVD8w+OX4lJvpwBiNUq 34AETQFV9bT/LHrFfIRxqM5UtwOYUr9fipF1FoEPf5ayhrRK1AmZ9C8G X-Gm-Gg: AeBDietHPy9OrdWJ3bBYhH/0GDemmUDBpB3+DMkYgjoW4aDtai7Bh399cDTJeO6EQKC /YFQw0pyTqwGJ69uQppXU70A6OKmV+XnqahwCUwLGJK9TT1Hf/ZxY0GdmFYDKSuHjnGYxyc27FJ 8726/AH/lU9TgZumhUM0OaI6i7Nw2USkDlFc06OEG7UZ4k1tUvjaJmkDbLNpNUI5fUKIVvetFvf M/71AMkgq8F2JLfqXM5ytSw2bxrT5TNQWttRY3aUqt5mC10bZwReoLdkcEsQmUEF5LuMyqKTEaK BSjXKtlHPkE6B0xy7+i4Y2QfQ2vJimk0Wdpc9Knyy/Kt/Plb6inc1e3x7DB9KFFnsapsLAll73F 1OwCArRMxeu6Cqhb08OTb8kisDLNe9R9whEu3KrVzv5COH1DGL01bI5QRKu0pC/9P7GD7ACHTih qVXRRXBQogzgD1iyCmkp9vbCoxTyZzlEvF0CAfRT1j2Iyrk9QUdAcWPgHv6dnqut7vJKu+em4= X-Received: by 2002:a05:600c:524a:b0:488:926e:3ccd with SMTP id 5b1f17b1804b1-488d7f24014mr123925205e9.4.1776168715997; Tue, 14 Apr 2026 05:11:55 -0700 (PDT) Received: from hackers.camp ([2a01:cb1c:784:2f00:708:2805:7128:7a75]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-488ede156a1sm49028485e9.2.2026.04.14.05.11.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 14 Apr 2026 05:11:55 -0700 (PDT) Received: (nullmailer pid 12724 invoked by uid 1000); Tue, 14 Apr 2026 14:11:31 -0000 From: Aurelien DESBRIERES To: Darrick J. Wong Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk, brauner@kernel.org Subject: Re: [RFC PATCH 06/10] ftrfs: add block and inode allocator In-Reply-To: <20260413152101.GX6202@frogsfrogsfrogs> References: <20260413142357.515792-1-aurelien@hackers.camp> <20260413142357.515792-7-aurelien@hackers.camp> <20260413152101.GX6202@frogsfrogsfrogs> Content-Type: text/plain; charset=UTF-8 Date: Tue, 14 Apr 2026 16:11:31 +0200 Message-Id: <1776175891.838384.12723.nullmailer@hackers.camp> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: On Mon, Apr 13, 2026 at 08:21:01AM -0700, Darrick J. Wong wrote: > No journalling? Or even COW metadata? How is this fault tolerant?? Fair question. The answer is that FTRFS fault tolerance is at the block data layer via Reed-Solomon FEC, not at the metadata consistency layer via journalling or COW. The threat model is radiation-induced single-event upsets (SEU) causing silent bit flips in data at rest on MRAM or NOR flash. Journalling protects against crash consistency (power loss mid-write). COW protects against torn writes. Neither corrects a bit flip that occurred while the device was idle and powered. RS FEC corrects up to 8 symbol errors per 255-byte subblock in place, without requiring a redundant copy. That is the specific gap that FTRFS addresses. The Radiation Event Journal (added in v3) provides a persistent log of every correction event in the superblock, giving operators a map of physical degradation over time. Journalling for crash consistency is a valid concern for v4. The current design assumes the target environment (space, avionics) has well-defined power cycles and controlled shutdown procedures, which reduces the crash consistency risk relative to general-purpose use. This will be documented explicitly in v4. Aurelien DESBRIERES