From: Denis Roy <denisjroy@gmail.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS critical (device md126): corrupt node: root=1 block=13404298215424 slot=307, unaligned pointer, have 12567101254720864896 should be aligned to 4096
Date: Fri, 8 Jul 2022 22:20:40 -0400 [thread overview]
Message-ID: <5e151f0f-7600-168e-66e3-f8fbf48953ca@gmail.com> (raw)
In-Reply-To: <18274afe-32ac-6014-c64a-ea041e61d927@gmx.com>
root@nas:~# btrfs check /dev/md126
ERROR: cannot open file system
that didn't work
On 2022-07-08 10:18 p.m., Qu Wenruo wrote:
>
>
> On 2022/7/9 10:16, Denis Roy wrote:
>> so, what option should I use?
>>
>>
>> btrfs check [options] /dev/md126??
>
> No option needed. That would be good enough.
>
> Or you may try "btrfs check --mode=lowmem" to provide a better readable
> output, but much slower.
>
> Thanks
> Qu
>>
>>
>>
>> On 2022-07-06 10:19 p.m., Qu Wenruo wrote:
>>
prev parent reply other threads:[~2022-07-09 2:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 1:32 BTRFS critical (device md126): corrupt node: root=1 block=13404298215424 slot=307, unaligned pointer, have 12567101254720864896 should be aligned to 4096 Denis Roy
2022-07-07 2:19 ` Qu Wenruo
2022-07-07 16:56 ` David Sterba
2022-07-08 5:50 ` Denis Roy
2022-07-08 6:00 ` Qu Wenruo
2022-07-08 6:20 ` Denis Roy
2022-07-08 7:04 ` Qu Wenruo
2022-07-09 1:34 ` Denis Roy
2022-07-09 1:48 ` Qu Wenruo
2022-07-09 1:53 ` Denis Roy
2022-07-07 19:56 ` Denis Roy
2022-07-09 2:16 ` Denis Roy
2022-07-09 2:18 ` Qu Wenruo
2022-07-09 2:20 ` Denis Roy [this message]
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=5e151f0f-7600-168e-66e3-f8fbf48953ca@gmail.com \
--to=denisjroy@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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.