From: Goffredo Baroncelli <kreijack@libero.it>
To: Nathan Henrie <nate@n8henrie.com>, linux-btrfs@vger.kernel.org
Subject: Re: BTRFS RAID1 root corrupt and read-only
Date: Thu, 1 Dec 2022 19:52:48 +0100 [thread overview]
Message-ID: <15a497f7-f4f0-6b17-0f90-58b5420aaaaf@libero.it> (raw)
In-Reply-To: <debfa7c5-646c-4333-a277-62e98a78a47e@app.fastmail.com>
On 01/12/2022 19.27, Nathan Henrie wrote:
> Hello all,
>
> I've been happily running a BTRFS RAID1 root across 3 x 1TB NVME drives on my Arch Linux machine for a few years with minimal (mostly quota-related) issues.
>
> I ran balance a few days ago that failed, and then my root went read-only. I found some smartd errors in one drive, so I
[...]
> [99537.333018] BTRFS info (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 12, gen 0
> [99537.333023] BTRFS info (device nvme0n1p1): bdev /dev/nvme1n1p1 errs: wr 0, rd 0, flush 0, corrupt 12, gen 0
I am not sure how is related; but from the above excerpt of dmesg, I see that both nvme0 and nvme1 have errors (== corruption). If this is true, raid1 is not enough to protect against these.
--
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:[~2022-12-01 18:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 18:27 BTRFS RAID1 root corrupt and read-only Nathan Henrie
2022-12-01 18:52 ` Goffredo Baroncelli [this message]
[not found] ` <69614c04-38e3-4b8a-8285-706c1bbc4618@app.fastmail.com>
2022-12-01 19:42 ` Nathan Henrie
2022-12-01 20:14 ` Remi Gauvin
2022-12-01 23:05 ` Nathan Henrie
2022-12-01 23:16 ` Qu Wenruo
2022-12-02 0:26 ` Nathan Henrie
2022-12-02 1:10 ` Qu Wenruo
2022-12-02 1:32 ` Nathan Henrie
2022-12-13 16:22 ` Nathan Henrie
2022-12-01 23:14 ` Qu Wenruo
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=15a497f7-f4f0-6b17-0f90-58b5420aaaaf@libero.it \
--to=kreijack@libero.it \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=nate@n8henrie.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.