From: "Sébastien Luttringer" <seblu@seblu.net>
To: Artem Mygaiev <joculator@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Corrupted filesystem, looking for guidance
Date: Wed, 13 Feb 2019 00:50:39 +0100 [thread overview]
Message-ID: <d9a44122e928f3a6cb03391364f63b7e1a49fafb.camel@seblu.net> (raw)
In-Reply-To: <CAJwc6KuhZuHve3FLbTcfbKUL8=WXmHN=OWnvDPJc4=pZQJsHWg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
On Tue, 2019-02-12 at 14:31 +0200, Artem Mygaiev wrote:
> Have same issue (RAID5 over 4 disks):
> https://marc.info/?l=linux-btrfs&m=154815802313248&w=2
>
> Having perfectly healthy HDDs it seem to be caused by some bit flips
> in SDRAM which is non-ECC in my case, unfortunately. Tried --repair,
> didn't helped, same for --init-csum-tree. Now using fs in ro mode
> (data is fully available), preparing for total rebuild.
>
> -- Artem
>
Thanks for sharing your misadventure. I'm a step ahead from you, as this issue
is on my rebuilt btrfs filesystem. 😎
What make you think it could be RAM bit flips?
Regards,
Sébastien "Seblu" Luttringer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 821 bytes --]
next prev parent reply other threads:[~2019-02-12 23:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 3:16 Corrupted filesystem, looking for guidance Sébastien Luttringer
2019-02-12 12:05 ` Austin S. Hemmelgarn
2019-02-12 12:31 ` Artem Mygaiev
2019-02-12 23:50 ` Sébastien Luttringer [this message]
2019-02-12 22:57 ` Chris Murphy
[not found] ` <CAJCQCtQ+b9y7fBXPPhB-gQrHAH-pCzau6nP1OabsC1GNqNnE1w@mail.gmail.com>
2019-02-18 20:14 ` Sébastien Luttringer
2019-02-18 21:06 ` Chris Murphy
2019-02-23 18:14 ` Sébastien Luttringer
2019-02-24 0:00 ` Chris Murphy
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=d9a44122e928f3a6cb03391364f63b7e1a49fafb.camel@seblu.net \
--to=seblu@seblu.net \
--cc=joculator@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).