From: Nazar Mokrynskyi <nazar@mokrynskyi.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: bad metadata [125501440, 125517824) crossing stripe boundary
Date: Wed, 16 Mar 2016 05:55:08 +0200 [thread overview]
Message-ID: <506b0d75-da00-fc77-e2ee-a5bf60abcf9f@mokrynskyi.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]
I was running btrfsck today and got many of such errors:
> bad metadata [125501440, 125517824) crossing stripe boundary
> bad metadata [131334144, 131350528) crossing stripe boundary
> bad metadata [142999552, 143015936) crossing stripe boundary
> bad metadata [153944064, 153960448) crossing stripe boundary
> bad metadata [281870336, 281886720) crossing stripe boundary
> bad metadata [528285696, 528302080) crossing stripe boundary
> bad metadata [661323776, 661340160) crossing stripe boundary
> bad metadata [986316800, 986333184) crossing stripe boundary
> bad metadata [987168768, 987185152) crossing stripe boundary
> bad metadata [1029111808, 1029128192) crossing stripe boundary
> bad metadata [1099169792, 1099186176) crossing stripe boundary
I was able to find message with similar error on mainling list from
January, but didn't found any answer.
I'm on Kernel 4.5.0 stable and btrfs-tools 4.4. filesystem was created
at the beginning of July 2015.
Here is btrfs scrub output:
> scrub status for 40b8240a-a0a2-4034-ae55-f8558c0343a8
> scrub started at Wed Mar 16 04:13:54 2016 and finished after
> 00:52:51
> total bytes scrubbed: 274.05GiB with 0 errors
Looks like no metadata errors found, so what that "bad metadata" things
really mean?
--
Sincerely, Nazar Mokrynskyi
github.com/nazar-pc
Skype: nazar-pc
Diaspora: nazarpc@diaspora.mokrynskyi.com
Tox: A9D95C9AA5F7A3ED75D83D0292E22ACE84BA40E912185939414475AF28FD2B2A5C8EF5261249
[-- Attachment #2: ÐÑÑпÑогÑаÑÑÑний пÑÐ´Ð¿Ð¸Ñ S/MIME --]
[-- Type: application/pkcs7-signature, Size: 3825 bytes --]
reply other threads:[~2016-03-16 3:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=506b0d75-da00-fc77-e2ee-a5bf60abcf9f@mokrynskyi.com \
--to=nazar@mokrynskyi.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).