On Tue, May 13, 2014 at 12:26 AM, Marc MERLIN <marc@xxxxxxxxxxx> wrote: > On Sat, May 10, 2014 at 04:57:18PM -0700, Marc MERLIN wrote: >> On Sat, May 10, 2014 at 03:42:49PM -0700, Marc MERLIN wrote: >> > I tried with 3.14.3 and it went further, however it died with >> > legolas:/mnt/btrfs_pool2# btrfs send home_ro.20140507_10:00:01 | btrfs receive /mnt/btrfs_pool1/ >> > At subvol home_ro.20140507_10:00:01 >> > At subvol home_ro.20140507_10:00:01 >> > ERROR: send ioctl failed with -5: Input/output error >> > ERROR: unexpected EOF in stream. >> > >> > I'll look up -5 later when I have time, but I guess there is a problem >> > on the source that is causing copies to fail with both kernels? >> >> This brings me back to the earlier question: >> >> When my other FS died, scrub ran ok just earlier. >> >> Now, having 2 btrfs sends (not incremental, full) fail with 2 kernels >> would indicate that something might be wrong on the source filesystem. > > So I copied the entire FS back to the SSD using rsync instead of btrfs > send/receive and as far as I can tell all the data got over fine. > > Is there anything you'd like from the subvolumes on the source that > btrfs cannot process and that I'm going to delete so that I can start > syncing back from the SSD to the HDD? For the issue you had with send sending weird path names, I just found a case that leads to it (or a crash or some other weird stuff): https://patchwork.kernel.org/patch/4170401/ But you really need to be using a lot of hard links and deleting them, so maybe it's caused by something else. thanks > > Thanks, > Marc > -- > "A mouse is a device used to point at the xterm you want to type in" - A.S.R. > Microsoft is to operating systems .... > .... what McDonalds is to gourmet cooking > Home page: http://marc.merlins.org/ | PGP 1024R/763BE901 -- Filipe David Manana, "Reasonable men adapt themselves to the world. Unreasonable men adapt the world to themselves. That's why all progress depends on unreasonable men." -- 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
