Hi Marc, This seems a regression which has been fixed by the following commit(only pushed into btrfs-next): https://git.kernel.org/cgit/linux/kernel/git/josef/btrfs-next.git/commit/?id=1334bebe71bebbca47b3b92f25511ea980fdeab8 Thanks, Wang On 02/25/2014 02:36 PM, 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 > > Anything else? > > Thanks, > Marc -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
