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 E77ABC4332F for ; Sun, 27 Nov 2022 22:11:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229563AbiK0WLe (ORCPT ); Sun, 27 Nov 2022 17:11:34 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46710 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229533AbiK0WLd (ORCPT ); Sun, 27 Nov 2022 17:11:33 -0500 Received: from mail.thelounge.net (mail.thelounge.net [91.118.73.15]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D467565EE for ; Sun, 27 Nov 2022 14:11:32 -0800 (PST) Received: from [10.10.10.2] (rh.vpn.thelounge.net [10.10.10.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) (Authenticated sender: h.reindl@thelounge.net) by mail.thelounge.net (THELOUNGE MTA) with ESMTPSA id 4NL2r00zgRzXLf; Sun, 27 Nov 2022 23:11:28 +0100 (CET) Message-ID: <5834d66a-21b8-767f-0dea-927dc749b83a@thelounge.net> Date: Sun, 27 Nov 2022 23:11:27 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Subject: Re: how do i fix these RAID5 arrays? Content-Language: en-US To: Wol , piergiorgio.sartor@nexgo.de, John Stoffel Cc: David T-G , Linux RAID list References: <20221123220736.GD19721@jpo> <20221124032821.628cd042@nvm> <20221124211019.GE19721@jpo> <25474.28874.952381.412636@quad.stoffel.home> <0c7ad6eff626c8440734909300ebc50d9b1bf615@nexgo.de> <4379b4f4-9e7f-a7dc-fc29-6c22b12bf3ea@thelounge.net> <531e8606-94b4-d48b-1d5a-72cc7d078755@youngman.org.uk> From: Reindl Harald Organization: the lounge interactive design In-Reply-To: <531e8606-94b4-d48b-1d5a-72cc7d078755@youngman.org.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-raid@vger.kernel.org Am 27.11.22 um 23:05 schrieb Wol: > And no, you are COMPLETELY WRONG in assuming that the only block layers > that implement trim is hardware. from a layered point of view my vmware vmdk-disk supporting trim still are hardware > Any block layer that wants to can > implement trim - there is no reason whatsoever why mdadm couldn't. I > never said it had, I said I wish it did but when it comes to reality nobody cares what you wish when i outline the differences in the real world in the real world mdadm don't anything you wish but what it does