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 X-Spam-Level: X-Spam-Status: No, score=-5.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 58FA0C433DB for ; Wed, 24 Feb 2021 09:52:28 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 0687164DE7 for ; Wed, 24 Feb 2021 09:52:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234568AbhBXJw0 (ORCPT ); Wed, 24 Feb 2021 04:52:26 -0500 Received: from mail02.aqueos.net ([94.125.164.151]:27932 "EHLO mail02.aqueos.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234454AbhBXJwC (ORCPT ); Wed, 24 Feb 2021 04:52:02 -0500 X-Greylist: delayed 490 seconds by postgrey-1.27 at vger.kernel.org; Wed, 24 Feb 2021 04:52:01 EST Received: from localhost (localhost [127.0.0.1]) by mail02.aqueos.net (Postfix) with ESMTP id 60C0A1A0CDB for ; Wed, 24 Feb 2021 10:43:08 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mail02.aqueos.net Received: from mail02.aqueos.net ([127.0.0.1]) by localhost (mail02.aqueos.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id T2vxWAI3Xo7r for ; Wed, 24 Feb 2021 10:43:07 +0100 (CET) Received: from [10.10.10.10] (adsl2.aqueos.com [185.63.172.127]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail02.aqueos.net (Postfix) with ESMTPSA id 9180B1A0CCA for ; Wed, 24 Feb 2021 10:43:07 +0100 (CET) To: linux-btrfs@vger.kernel.org From: Ghislain Adnet Subject: btrfd, is btrfs daemon a thing ? Organization: AQUEOS Message-ID: <900f07e8-251f-de6f-1fcf-0168ca3ad72d@aqueos.com> Date: Wed, 24 Feb 2021 10:43:06 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org hi there, As a newbie in Btrfs land i installed a raid1 configuration and played with it. After hot removing a drive of the raid i got two remarks that i cannot find answer with with my google foo. So, to not die stupid i post a little email here to see if there is solutions about this :) The experiment finished well the raid was reconstructed ans some untouched partition were even recreated automaticaly when the drive was put back, this is very cool ! The one with changes had to be manualy replaced, that was espected. The issues are: - logs: my systemd journal and my kernel.log were completely stampeded by btrfs logs. On the mdadm world you have some message about disapearing drives and then it stops. On my test there was hundreds of megabytes of brtfs error logs. - monitoring : on mdamd you have a daemon that can warn you and even automaticaly run programs to warn you of a failure. I think zfs has this too with ZED. I was not able to find such a thing in btrfs. Does it exist such a monitoring system capable of warning the admin when error appear in btrfs other than cron grepping the logs or btrfs device stats ? Is there anyway to mitigate the log issue and did someone took a shot at a monitoring system for btrfs ? -- best regards, Ghislain.