On 05/06/2014 08:10 AM, David Brown wrote:
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
--
I am also seeing this on 3.14.1 (on ArchLinux). Scrub also reports no
errors.
I could also not do a ful send. Balancing made it better for a while (I
was able to send a full snapshot of one subvolume, but not another), but
it did not help. Offline repairing the fs with btrfsck --repair also did
not affect it.
Blaz
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
