From: Marc Joliet <marcec@gmx.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: [4.7.2] btrfs_run_delayed_refs:2963: errno=-17 Object already exists
Date: Mon, 06 Mar 2017 00:53:40 +0100 [thread overview]
Message-ID: <2713353.CA3Dyp7XXF@thetick> (raw)
In-Reply-To: <14737660.8idzxVKBRv@thetick>
[-- Attachment #1: Type: text/plain, Size: 2015 bytes --]
On Mittwoch, 1. März 2017 19:14:07 CET you wrote:
> In any
> case, I started btrfs-check on the device itself.
*Sigh*, I had to restart it, because I forgot to redirect to a file and quite
frankly wasn't expecting this flood of output, but here's a summary of the
output after about 2 days:
% wc -l btrfs_check_output_20170303.log
1360252 btrfs_check_output_20170303.log
% grep -v "backref lost" btrfs_check_output_20170303.log | grep -v "check \
(leaf\|node\) failed" | grep -v "lost its parent" | grep -v "referencer count"
checking extents
ERROR: block group[3879328546816 1073741824] used 1072840704 but extent items
used 1129164800
ERROR: block group[4163870130176 1073741824] used 1072259072 but extent items
used 0
ERROR: block group[4223999672320 1073741824] used 1073664000 but extent items
used 1074188288
ERROR: block group[4278760505344 1073741824] used 1073377280 but extent items
used 1073901568
ERROR: block group[4406535782400 1073741824] used 1073627136 but extent items
used 0
ERROR: extent [3830028140544 4096] referencer bytenr mismatch, wanted:
3830028140544, have: 3826183847936
% tail btrfs_check_output_20170303.log
ERROR: data extent[3924538445824 4096] backref lost
ERROR: data extent[3933464903680 4096] backref lost
ERROR: data extent[3924538531840 4096] backref lost
ERROR: data extent[3839131480064 4096] backref lost
ERROR: data extent[3834701750272 4096] backref lost
ERROR: data extent[3873087918080 4096] backref lost
ERROR: data extent[3873072283648 4096] backref lost
ERROR: data extent[3873088090112 8192] backref lost
ERROR: data extent[3873072287744 4096] backref lost
ERROR: data extent[3856294449152 4096] backref lost
That's right, slowly approaching 1.5 million lines of btrfs-check output!
That's *way* more than I ran it the last time this error happened a few weeks
ago.
Greetings
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-03-05 23:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-28 13:29 [4.7.2] btrfs_run_delayed_refs:2963: errno=-17 Object already exists Kai Krakow
2017-02-02 12:01 ` Marc Joliet
2017-02-03 22:44 ` Kai Krakow
2017-02-10 22:15 ` Marc Joliet
2017-02-11 2:01 ` Kai Krakow
2017-02-11 10:18 ` Marc Joliet
2017-02-14 12:52 ` Marc Joliet
2017-02-17 8:19 ` Kai Krakow
2017-02-28 22:14 ` Marc Joliet
2017-03-01 8:23 ` Marc Joliet
2017-03-01 9:32 ` Qu Wenruo
2017-03-01 18:14 ` Marc Joliet
2017-03-01 18:27 ` Marc Joliet
2017-03-01 18:43 ` Marc Joliet
2017-03-02 9:44 ` Marc Joliet
2017-03-03 1:09 ` Qu Wenruo
2017-03-03 11:26 ` Marc Joliet
2017-03-05 23:53 ` Marc Joliet [this message]
2017-03-06 11:18 ` Marc Joliet
2017-03-02 0:43 ` Qu Wenruo
2017-03-02 9:43 ` Marc Joliet
2017-03-03 1:00 ` Qu Wenruo
2017-03-03 11:54 ` Marc Joliet
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=2713353.CA3Dyp7XXF@thetick \
--to=marcec@gmx.de \
--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).