From: Goffredo Baroncelli <kreijack@inwind.it>
To: Remi Gauvin <remi@georgianit.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS list of grievances
Date: Thu, 3 Oct 2024 20:24:23 +0200 [thread overview]
Message-ID: <2733d961-cef0-4fac-8a46-3d74f1c4bf7a@inwind.it> (raw)
In-Reply-To: <8236a191-88d5-b2bb-2048-87b49539a8a3@georgianit.com>
On 03/10/2024 19.26, Remi Gauvin wrote:
> On 2024-10-03 1:10 p.m., Goffredo Baroncelli wrote:
>>
>> $ sudo ./btrfs dev stat -T /mnt/btrfs-raid1/
>> Id Path Write errors Read errors Flush errors Corruption errors
>> Generation errors
>> -- --------- ------------ ----------- ------------ -----------------
>> -----------------
>> 1 /dev/sda2 0 0 0
>> 763 0
>> 2 /dev/sdb2 0 0 0
>> 3504 0
>> 3 /dev/sdd2 13 0 0
>> 6218 0
>>
>
> I hope that's a made up sample and not actual output of your
> filesystem. Otherwise, you have a problem...
>
It is a real output, and I didn't notice these errors.
This was an old disks set. And these are old errors, due to a bad power supply.
Replaced the power supply all the problem disappeared.
Of course I didn't have any data issue, due to btrfs+raid1.
However I never cared to clear those errors. Anyway I run a "btrfs scrub"
which didn't find any error.
BR
--
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2024-10-03 18:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 11:20 BTRFS list of grievances waxhead
2024-09-27 16:27 ` Roman Mamedov
2024-09-27 18:05 ` Remi Gauvin
2024-09-27 19:01 ` Colin S
2024-10-02 19:31 ` Chris Murphy
2024-10-02 23:18 ` Colin S
2024-09-28 10:15 ` Paul Jones
2024-09-28 17:51 ` Roman Mamedov
2024-09-27 17:44 ` Mark Harmstone
2024-09-30 21:43 ` Goffredo Baroncelli
2024-10-03 17:10 ` Goffredo Baroncelli
2024-10-03 17:26 ` Remi Gauvin
2024-10-03 18:24 ` Goffredo Baroncelli [this message]
2024-10-03 18:32 ` Remi Gauvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2733d961-cef0-4fac-8a46-3d74f1c4bf7a@inwind.it \
--to=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=remi@georgianit.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox