From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: Kenneth Bogert <kbogert@unca.edu>, linux-btrfs@vger.kernel.org
Subject: Re: Subvolume corruption after restart on Raid1 array
Date: Fri, 24 Feb 2017 01:15:54 +0100 [thread overview]
Message-ID: <d6787fb0-3bfc-987c-bdd8-33c154faa443@mendix.com> (raw)
In-Reply-To: <36F10428-FA2D-42F2-9065-8AFD7B6AF902@unca.edu>
On 02/23/2017 05:42 PM, Kenneth Bogert wrote:
>
>> On Feb 17, 2017, at 1:39 PM, Kenneth Bogert <kbogert@unca.edu> wrote:
>>
>> On Feb 11, 2017, at 12:34 PM, Kenneth Bogert <kbogert@unca.edu> wrote:
>>>
>>> kernel: BTRFS error (device sdb): parent transid verify failed on 1721409388544 wanted 19188 found 83121
>>> [...]
>
> Is anyone interested in this problem? If not, I’m planning on rebuilding this filesystem this weekend.
Only this: "kernel: BTRFS error (device sdb): parent transid verify
failed on 1721409388544 wanted 19188 found 83121" already makes me think
there's something gone horribly wrong here. And, my guess is that it
more likely has to do something with hardware than the btrfs program code.
If there's one bit that flipped it might be possible to rescue a
filesystem manually, but these transid mismatches sound like the
filesystem is encountering whole blocks of data that should never been
there in the first place. A whole bunch of writes never ended up on
disk, while a disk controller assured they would etc.
The lack of response should probably not be interpreted as "not caring",
but more like "I really don't know" and just like not mailing a whole
list with a "me too!" post, people won't mail "I don't know, dude, let's
go bowling" too much. Or, it might be possible, but only realistically
done when travelling to you, getting to work with your computer and then
spending hours to find out what to do.
--
Hans van Kranenburg
next prev parent reply other threads:[~2017-02-24 0:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-11 17:34 Subvolume corruption after restart on Raid1 array Kenneth Bogert
2017-02-17 18:39 ` Kenneth Bogert
2017-02-23 16:42 ` Kenneth Bogert
2017-02-24 0:15 ` Hans van Kranenburg [this message]
2017-02-25 19:00 ` Kenneth Bogert
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=d6787fb0-3bfc-987c-bdd8-33c154faa443@mendix.com \
--to=hans.van.kranenburg@mendix.com \
--cc=kbogert@unca.edu \
--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 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.