Success! Using the same ISO you previously linked to, I ran 'btrfs check --repair', did another check which actually revealed many new issues, ran a repair again and after that successive checks showed no signs of other issues. I was able to successfully send my 'home' subvolume to the SSD and wow, huge difference with otherwise little effort. Thanks to you and everybody else for helping me resolve this issue. On Tue, Mar 22, 2016 at 8:34 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > On Tue, Mar 22, 2016 at 7:40 PM, Ryan Erato <rerato@xxxxxxxxx> wrote: >> Finally got around to running the suggested commands. Same error with >> the send, but not much output to help. The check operation did seem >> to reveal some potential issues. Here's the play-by-play along with >> the file output from check: >> >> [liveuser@localhost /]$ sudo btrfs check /dev/sda6 > >> /home/liveuser/btrfscheck.txt >> checking extents >> checking free space cache >> checking fs roots >> root 257 inode 13324701 errors 200, dir isize wrong >> root 258 inode 226392 errors 200, dir isize wrong >> root 258 inode 236055 errors 2000, link count wrong >> unresolved ref dir 226392 index 35 namelen 7 name LOG.old filetype 0 >> errors 3, no dir item, no dir index >> root 258 inode 236273 errors 2000, link count wrong >> root 258 inode 236276 errors 2000, link count wrong >> unresolved ref dir 226392 index 39 namelen 15 name MANIFEST-000015 >> filetype 0 errors 3, no dir item, no dir index >> root 258 inode 236277 errors 2000, link count wrong >> unresolved ref dir 226392 index 41 namelen 7 name CURRENT filetype 0 >> errors 3, no dir item, no dir index >> root 258 inode 240618 errors 2000, link count wrong >> unresolved ref dir 226392 index 115 namelen 10 name 000089.log >> filetype 0 errors 3, no dir item, no dir index >> root 487 inode 13324701 errors 200, dir isize wrong >> root 488 inode 226392 errors 200, dir isize wrong >> root 488 inode 236055 errors 2000, link count wrong >> unresolved ref dir 226392 index 35 namelen 7 name LOG.old filetype 0 >> errors 3, no dir item, no dir index >> root 488 inode 236273 errors 2000, link count wrong >> root 488 inode 236276 errors 2000, link count wrong >> unresolved ref dir 226392 index 39 namelen 15 name MANIFEST-000015 >> filetype 0 errors 3, no dir item, no dir index >> root 488 inode 236277 errors 2000, link count wrong >> unresolved ref dir 226392 index 41 namelen 7 name CURRENT filetype 0 >> errors 3, no dir item, no dir index >> root 488 inode 240618 errors 2000, link count wrong >> unresolved ref dir 226392 index 115 namelen 10 name 000089.log >> filetype 0 errors 3, no dir item, no dir index > > OK so now the question is if 'btrfs check --repair' can fix this, and > what version to use? 4.4.1 or 4.5.0? Based on the changelog, you can > probably use either version. And I think it should be safe. But, you > should still have backups seeing as you can mount the volume. > > >> >> [liveuser@localhost /]$ sudo mount /dev/sda6 /mnt/hdd >> >> [liveuser@localhost /]$ sudo btrfs send -vvv --no-data -f homesnap.btr >> /mnt/hdd/home/home.snap/ >> Mode NO_FILE_DATA enabled >> At subvol /mnt/hdd/home/home.snap/ >> ERROR: send ioctl failed with -2: No such file or directory > > OK so there's something off with the metadata and it's not going to do > a send as a result is what this sounds like to me. > > > -- > Chris Murphy -- 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
