My full backup still doesn't complete. However, instead of hanging the entire disk subsystem as it did on 111b, it now issues error messages. Errors at the end.
sending from @bup-daily-20100726-100000CDT to zp1/d...@bup-daily-20100727-100000cdt received 3.80GB stream in 136 seconds (28.6MB/sec) receiving incremental stream of zp1/d...@bup-daily-20100727-100000cdt into bup-wrack/fsfs/z p1/d...@bup-daily-20100727-100000cdt sending from @bup-daily-20100727-100000CDT to zp1/d...@bup-daily-20100728-100001cdt received 192MB stream in 10 seconds (19.2MB/sec) receiving incremental stream of zp1/d...@bup-daily-20100728-100001cdt into bup-wrack/fsfs/z p1/d...@bup-daily-20100728-100001cdt sending from @bup-daily-20100728-100001CDT to zp1/d...@bup-daily-20100729-100000cdt received 170MB stream in 9 seconds (18.9MB/sec) receiving incremental stream of zp1/d...@bup-daily-20100729-100000cdt into bup-wrack/fsfs/z p1/d...@bup-daily-20100729-100000cdt sending from @bup-daily-20100729-100000CDT to zp1/d...@bup-2hr-20100729-220000cdt warning: cannot send 'zp1/d...@bup-2hr-20100729-220000cdt': no such pool or dataset sending from @bup-2hr-20100729-220000CDT to zp1/d...@bup-2hr-20100730-000000cdt warning: cannot send 'zp1/d...@bup-2hr-20100730-000000cdt': no such pool or dataset sending from @bup-2hr-20100730-000000CDT to zp1/d...@bup-2hr-20100730-020000cdt warning: cannot send 'zp1/d...@bup-2hr-20100730-020000cdt': no such pool or dataset sending from @bup-2hr-20100730-020000CDT to zp1/d...@bup-2hr-20100730-040000cdt warning: cannot send 'zp1/d...@bup-2hr-20100730-040000cdt': incremental source (@bup-2hr-20 100730-020000CDT) does not exist sending from @bup-2hr-20100730-040000CDT to zp1/d...@bup-2hr-20100730-060000cdt sending from @bup-2hr-20100730-060000CDT to zp1/d...@bup-2hr-20100730-080000cdt sending from @bup-2hr-20100730-080000CDT to zp1/d...@bup-daily-20100730-100000cdt sending from @bup-daily-20100730-100000CDT to zp1/d...@bup-2hr-20100730-100000cdt sending from @bup-2hr-20100730-100000CDT to zp1/d...@bup-2hr-20100730-120000cdt sending from @bup-2hr-20100730-120000CDT to zp1/d...@bup-2hr-20100730-140000cdt sending from @bup-2hr-20100730-140000CDT to zp1/d...@bup-2hr-20100730-160000cdt sending from @bup-2hr-20100730-160000CDT to zp1/d...@bup-2hr-20100730-180000cdt sending from @bup-2hr-20100730-180000CDT to zp1/d...@bup-2hr-20100730-200000cdt sending from @bup-2hr-20100730-200000CDT to zp1/d...@bup-2hr-20100730-220000cdt received 162MB stream in 9 seconds (18.0MB/sec) receiving incremental stream of zp1/d...@bup-2hr-20100730-060000cdt into bup-wrack/fsfs/zp1 /d...@bup-2hr-20100730-060000cdt cannot receive incremental stream: most recent snapshot of bup-wrack/fsfs/zp1/ddb does not match incremental source bash-4.0$ The bup-wrack pool was newly-created, empty, before this backup started. The backup commands were: zfs send -Rv "$srcsnap" | zfs recv -Fudv "$BUPPOOL/$HOSTNAME/$FS" I don't see how anything could be creating snapshots on bup-wrack while this was running. That pool is not normally mounted (it's on a single external USB drive, I plug it in for backups). My script for doing regular snapshots of zp1 and rpool doesn't reference any of the bup-* pools. I don't see how this snapshot mismatch can be coming from anything but the send/receive process. There are quite a lot of snapshots; dailys for some months, 2-hour ones for a couple of weeks. Most of them are empty or tiny. Next time I will try WITHOUT -v on both ends, and arrange to capture the expanded version of the command with all the variables filled in, but I don't expect any different outcome. Any other ideas? -- David Dyer-Bennet, d...@dd-b.net; http://dd-b.net/ Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/ Photos: http://dd-b.net/photography/gallery/ Dragaera: http://dragaera.info _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
