From: David Brown <davidb@davidb.org>
To: Marc MERLIN <marc@merlins.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: 3.14.0rc3: did not find backref in send_root
Date: Mon, 5 May 2014 23:10:54 -0700 [thread overview]
Message-ID: <20140506061053.GA17689@davidb.org> (raw)
In-Reply-To: <20140225063652.GD3521@merlins.org>
On Mon, Feb 24, 2014 at 10:36:52PM -0800, Marc MERLIN wrote:
>I got this during a btrfs send:
>BTRFS error (device dm-2): did not find backref in send_root. inode=22672, offset=524288, disk_byte=1490517954560 found extent=1490517954560
>
>I'll try a scrub when I've finished my backup, but is there anything I
>can run on the file I've found from the inode?
>
>gargamel:/mnt/dshelf1/Sound# btrfs inspect-internal inode-resolve -v 22672 file.mp3
>ioctl ret=0, bytes_left=3998, bytes_missing=0, cnt=1, missed=0
>file.mp3
I've just seen this error:
BTRFS error (device sda4): did not find backref in send_root. inode=411890, offset=307200, disk_byte=48100618240 found extent=48100618240
during a send between two snapshots I have.
after moving to 3.14.2. I've seen it on two filesystems now since
moving to 3.14. I have the two readonly snapshots if there is
anything helpful I can figure out from them.
Scrub reports no errors, but I don't seem to be able to back up
anything now.
David
next prev parent reply other threads:[~2014-05-06 6:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 6:36 3.14.0rc3: did not find backref in send_root Marc MERLIN
2014-02-25 7:50 ` Wang Shilong
2014-02-25 17:30 ` 3.14.0rc3: btrfs send ioctl failed with -5: Input/output error Marc MERLIN
2014-02-26 3:38 ` Wang Shilong
2014-02-26 7:46 ` 3.14.0rc3: did not find backref in send_root Marc MERLIN
2014-02-26 7:51 ` Wang Shilong
2014-02-26 17:16 ` Marc MERLIN
2014-05-06 6:10 ` David Brown [this message]
2014-05-06 6:49 ` Blaz Repas
2014-05-10 8:13 ` David Brown
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=20140506061053.GA17689@davidb.org \
--to=davidb@davidb.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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).